http://openmoko.org/api.php?action=feedcontributions&user=DolfjeBot1&feedformat=atomOpenmoko - User contributions [en]2024-03-28T14:06:48ZUser contributionsMediaWiki 1.19.24http://openmoko.org/wiki/Wishlist_-_Hardware_-_Novel_DevicesWishlist - Hardware - Novel Devices2008-08-31T13:03:36Z<p>DolfjeBot1: Replacing 'Freerunner' with 'FreeRunner'</p>
<hr />
<div>This page details hardware some would like in future Openmoko devices that are very different from the [[Neo1973]]. DVD/media players, cameras, ...<br />
<br />
=== Hard Drive ===<br />
Providing a hard drive, will allow storing music, movies, etc. Add USB storage device capability to use the device as an external hard drive.<br />
<br />
=== Openmoko-branded modem card ===<br />
<br />
A 3G modem card for use with other computing hardware, in particular PCs. Probably an internal expansion card such as an ExpressCard or Compact Flash card, with an alternative external (USB) unit for computers without internal slots. (In fact, a PCI-factor internal card for desktop computers might be reasonable too; see below.)<br />
<br />
There are already CardBus and external USB 3G modems available. In hardware terms, Openmoko's modem could well be a simple rebranding of one of these existing products. But, at least in some areas, the 3G modem products available to end-users tend to be tied to a particular telco and bundled with that telco's software. They also have a mysterious tendency not to actually allow voice calls over the modem, even when the modem hardware appears to be quite capable of it. An Openmoko modem that simply provided open drivers, no lock to a particular telco, good support for various operating systems, and simple support for voice and video calls over the modem, all out of the box, would already have some fairly unique selling points. (Since video conferencing is now taking off on personal computers, hardware that allows your desktop computer to make video calls to 3G mobile phones might well have a market, which is one reason why a PCI-factor card might not be so crazy.)<br />
<br />
But more than that, any software or services that Openmoko develops to overcome the tricky problems of juggling and integrating different Internet and phone connections and different email, IM, VoIP and telephone-number identities on Internet-enabled phones would be available to users of the Openmoko modem too. That would be a powerful selling point for the modem if and when Openmoko has compelling solutions to these problems. In fact, the increased integration with PCs would make all Openmoko devices more attractive. ("Whenever I'm logged in to my laptop all my calls go there, even when I'm not in range of WiFi.")<br />
<br />
Since [[FIC]] already has well-established relationships in the PC world, it could presumably make good use of those connections in selling the modems.<br />
<br />
* Obviously the Openmoko modem faces much the same problems with getting reasonably open access to 3G hardware that are delaying 3G for the [[Neo1973]] series <br />
<br />
* Naturally a 3G Neo1973 or other Openmoko phone would (or should) be able to provide many of the same advantages when acting as a modem for a PC. But there will still be a place for dedicated modems, if only because yoking a full mobile phone to your computer isn't always the best solution <br />
<br />
* Just like full phones, modems would benefit from support for multiple SIMs (see [[Wish_List_-_Hardware#Ability_to_use_multiple_SIMs.2Fnetworks]]) if they're going to be used for (non-VoIP) voice<br />
<br />
* Bonus points if the hardware provides a POTS landline connection and the software can juggle it along with 3G and Internet connections...<br />
<br />
=== PCMCIA slot ===<br />
Extensibility would be nice. Standard pcmcia would be great for allowing wireless too. And pcmcia cards tend to be very low power.<br />
*1. can be used for a spare battery (is this possible?)<br />
*3. i can use my [http://www.echoaudio.com/Products/CardBus/IndigoIO/index.php Echo Audio Indigo I/O]<br />
*2. can be used for different cards around<br />
<br />
This is certain not to happen in a production phone, it's simply far too large, and requires complex support in hardware, which does not exist in most system on a chip devices as are used in phones. <br />
Even for the [[Expansion_Back]] it would be too large. --[[User:Speedevil|Speedevil]] 06:05, 28 February 2007 (CET)<br />
<br />
== Cameras & Imaging ==<br />
==== See [[Wish_List_-_Hardware#Camera]] for additional/updated info on camera suggestions ====<br />
=== Interchangeable Camera Lenses ===<br />
<br />
A camera phone with a [http://en.wikipedia.org/wiki/Lens_mount lens mount] would allow swappable camera lenses and filters. Camera phones are usually stuck with tiny fixed lenses that don't allow focusing. Imaging being able to swap out the default lens with one that provides a better focus... or even a zoom! <br />
<br />
The C-Mount or [http://en.wikipedia.org/wiki/T-mount T-Mount] would be a good choice. Both are standard lens mount with many supporting lenses. Minolta, Canon, Nikon, Olympus, & most other lens manufacturers also have [http://www.bhphotovideo.com/c/shop/300/Lens_Adapters_Mounts.html mount adapters] for their proprietary lenses. Then share lenses between your camera & cell phone. The mount hole would need to be about 1 inch in diameter and go about 1/4 inch into the camera-phone (with the focal plane array chip at the bottom of this hole).<br />
<br />
CS-Mount would actually be better than a c mount because it requires 12.52mm from surface to imaging chip, instead of the 17.52mm required for c mounts.<br />
<br />
'''Added bonus If you work somewhere that doesn't allow cameras:'''<br />
The lens could be removed and a blank insert could be screwed in.<br />
The camera capability would be physically disabled!<br />
<br />
[[Image:Neo1973-ExpCamCS.png]] <br /><br />
concept image from [[Hardware:Neo1973:Alternate_Cases:Camera]]<br />
<br />
<br />
=== Business Card Reader ===<br />
This is probably technically difficult if not impossible, maybe you could do it with the embedded camera hardware & software<br />
<br />
I want to be able to place a business card face down on the the screen, and have the device automatically read the card and enter the info in the contacts.<br />
* There is no simple way of reading something placed on the screen, for the basic reason that the screen is in the way.<br />
* Of course you could always just take a picture of the card with a camera-phone. Then store it as it is or image recognition software could do character recognition & extract the information.<br />
<br />
=== Solar Panels ===<br />
My old pocket calculator had solar panels, why not my phone?<br />
See also: [[Expansion_Back#Ideas which require slight modifications of the phone.]]<br />
<br />
Here is my Solar Panel Mod for the Neo1973(GTA01) <br />
[[Image:http://i98.photobucket.com/albums/l274/subfunction/PIC-0007.jpg]] --KrisAbsinthe<br />
<br />
May be not so bad idea when you are somewhere in mountains and cannot easily charge the battery. This may at least prolong the battery life. [[User:AudriusA|AudriusA]] 17:56, 12 July 2008 (UTC)<br />
<br />
=== Fuel Cell ===<br />
Some people want to put them in laptops & fuel cells are the way of the future.<br />
<br />
===TV Out===<br />
With help of mouse and keyboard, a TV output may be very useful.<br />
Or to watch photos taken with a digital camera on holidays.<br />
Or for showing a slide presentation off.<br />
<br />
<br />
=== Larger Screen ===<br />
<br />
A model with a larger screen would be of use to many, especially with multi-touch. Higher resolution is probably less important than size until the DPI drops below 150 or so.<br />
<br />
<br />
=== Tiny Video Projector - "Beamer" ===<br />
<br />
At the [http://www.sid.org/conf/sid2007/sid2007.html DisplayWeek2007] several embeded video projectors for phones were presented. <br />
Those projecting devices are not much bigger than a cell phone. A LED-laser projects a sharp image at variable distance<br />
Could such a device be connected by bluetooth?<br />
[http://www.explay.co.il/ Explay] uses two a red and a green laser-LED as well as a conventional blue LED in its "oio".<br />
Blue laser-LED are to expensive for customer products. The light passes a transmissive WVGA-LCD(640x480) and goes on <br />
to the screen. Its frequency is 60Hz and the projecting distance can be varied from 20cm(8inch) to 2m(80inch) with <br />
a sharp picture. It consumes about 5W and its light power is about 6 lumen. As the sharpness does not depend on<br />
distance, one can project the image on screens that are not plane. Like someones t-shirt.<br />
<br />
[http://www.microvision.com/ Microvistions] PicoProjektor however uses soley laser-LEDs. It is also 60Hz though 800x600px or 800x640.<br />
<br />
Potential problems might become the approval of a laser class 3 device.<br />
<br />
Final prices could be about $300.<br />
Taken from: http://www.heise.de/newsticker/meldung/90141 (german)<br />
<br />
===HMD===<br />
Possibility to use something like [http://www.aeinnovations.com/projects/ver0/ Eyeglass Mounted Display].<br />
<br />
Or a HUD for use in a car windscreen. Needs a small projector attached to the phone. The phone is placed in front of the steering wheel on the console and displays information projected against the windscreen.<br />
<br />
===Multi I/O adapter===<br />
*VGA, standard Jack (line in & out), standard USB<br />
<br />
===Credit Card Swiper/Reader===<br />
*A credit card swipe function on the device, so that business operators can use the device to accept payments. In some markets a 'chip+pin' card reader may be an alternative. Existing devices are very expensive. Transaction information is sent over the internet, transaction "hub" services like 1stData could receive the data and reply with email receipts to the merchant, who could then forward the receipt to customer's email, or print a receipt on a bluetooth printer.<br />
<br />
===Modular hardware design / interchangeable components===<br />
It would be great to have several interchangeable components on the 'bus' of the device. Imagine opening the case and being able to add GPS to an empty internal bay or swap an Accelerometer for 3G support. <br />
Similar to the PCI hardware model of desktop PCs -- let savvy users swap and upgrade internal components by intentionally designing swappable components on some standardized bus.<br />
<br />
Unfortunately, this is a big problem for compact devices.<br />
To take the above examples. An accelerometer module may be 5mm*5mm*2mm. <br />
A 3G module 50mm*30mm*10mm, a GSM module 30mm*40mm*5mm and a GPS module 20mm*15mm*5mm. <br />
Apart from the wasted space problems, this means also that each module has to be custom-built for FIC. <br />
Then there is a second part - you have to have connectors and some way to clamp the module in place.<br />
<br />
This adds yet more weight and volume.<br />
--[[User:Speedevil|Speedevil]] 12:03, 29 June 2007 (CEST)<br />
<br />
==Audio & video==<br />
<br />
===In-dash car computer / tuner / cd-player ===<br />
<br />
I would love to see a FOSS, OpenMoko-powered in-dash car computer. I think there's a good market for it and component-wise it's probably easier and cheaper to build than the Neo phones (more off-the-self components, less hassle with parts under legal wraps like the Neo GSM chip). There are several possible versions of such hardware, ranging from similar to existing devices to completely innovative.<br />
<br />
A model similar to competing devices could be build from a standard 1-din case with a customized detachable front. Features: Tuner, RDS, CD player, USB port, aux line-in, Bluetooth, SD card slot. Except for the detachable front (which would have to be custom designed, or at the very least branded) most of the components are standard off-the-self components. The case is standardized and is large enough to hold a microATX or nanoATX board and a slim CD/DVD player such as found in laptops. Power supplies that hook to the car battery, USB, SD and Bluetooth are standard as well. Either on-board audio or an internal sound card can provide all the audio input and output required. The SD card slot and USB port could be put in the detachable front. That way you could simply take out the frame, hook it to your PC with a male-male USB cable and reprogram the device. No need to fiddle with the SD card. All this powered by the OpenMoko software stack of course.<br />
<br />
A more geeky version of the above could offer wifi for example (to communicate from your PC with the car that's in the garage. E.g. uploading new music). Or perhaps the USB slot in the front can be made a full USB host so you can use USB wifi sticks or other USB devices as well as standard USB storage.<br />
<br />
A more innovative version of such a device could be by embedding a big touch-screen LCD in the front of the device and optionally just one button: a knob that you can turn and push in. Resolution would have to match the aspect ratio of a standard 1-din device so it would probably be something like 1024x480 or 800x320. Such a device would also need a more capable graphics processor, perhaps one similar to the Neo FreeRunner capable of OpenGL ES. Touchscreen LCDs are common in car navigation equipment but to my knowledge have never been used on standard 1-din in-dash receivers before. You could get a very novel and elegant UI using this, much more elegant that in-dash receivers usually are.<br />
<br />
==Unsorted==<br />
<br />
===Virtual laser keyboard===<br />
see...<br />
http://www.virtual-laser-keyboard.com/?an=google<br />
<br />
== Different Shapes & Styles ==<br />
==== See [[Wish_List_-_Hardware#Casing]] for case suggestions & case mods ==== <br />
The current shape is great and many people love it (and I myself plan on getting one). Still, different strokes for different folks & we're allowed to muse about other options.<br />
<br />
<br />
===Dump the '''''egg-shaped''''' case design and go '''''rectangular''''' for more screen space===<br />
*I'm all for devices that look great and have great features - aside from that I really like the current design. Thus I'd like to comment that the design change request is probably not the majority's opinion. [[User:Abraxa|Abraxa]] 00:00, 18 February 2007 (CET)<br />
<br />
There will be many Openmoko devices, of different designs. --[[User:Speedevil|Speedevil]] 06:19, 28 February 2007 (CET)<br />
<br />
<br />
===Clamshell===<br />
Nuff said<br />
<br />
===Twisting top===<br />
Perfect for a multi-directional camera phone (for easier self photos & video conferencing)<br /><br />
[[Image:Kg920phone.jpg]]<br /><br />
<br />
===Alcohol Sensor===<br />
Alcohol sensor adjacent to microphone. It doesn't have to be accurate, just has to detect any amount of alcohol on the speaker's breath. I understand this is a very narrow market, but alcohol is on every parent's mind.<br />
<br />
I think those who drive cars might profit from this feature too. --[[User:Cedel|cedel]] 16:02, 20 February 2007 (CET)<br />
<br />
:Although this is a good idea, you have to be very careful about liability here. If it gives a false positive (i.e. you're not over the limit), and you have an accident, the Openmoko team might be liable.<br />
<br />
::I guess the good alcohol sensor is very expensive, cheap very often give false outcome. However, they more often produce negative (no alcohol) while there is. And there's still the thing about guilt Openmoko team would bear. --[[User:Tolein|tolein]] 18:01, 1 October 2007 (GMT+1)<br />
<br />
===Bottle opener===<br />
* including a bottle opener is very hard, but could be useful.<br />
* [http://www.bokonzept.de/php/images/462.jpg example]<br />
* It definitely is useful. A metal reinforced corner might be enough. While it is possible to open bottles with most cell phones, they don't look too good after opening a few cases.<br />
* Every multi-tool has to have a cork screw<br />
<br />
==Stackable Back Expansion plates==<br />
A reference specification for creating add-on devices. The phone has a back where other backs can be added and removed as the user desires depending on the function needed at the time supplied by each back expansion device. <br />
A USB 2.0 port which can use all usb devices such as a USB Storage or a Printer Etc.<br />
:Great idea, however it would require some other port, not USB. It should be thin, so it wouldn't take much space "inside" phone, and also should let you spin the add-on device, so it should be circular. --[[User:Tolein|tolein]] 18:02, 1 October 2007 (GMT+1)<br />
<br />
[[Category:Hardware ideas]]</div>DolfjeBot1http://openmoko.org/wiki/Wishlist/Software:GPS_proxyWishlist/Software:GPS proxy2008-08-31T13:03:22Z<p>DolfjeBot1: Replacing 'Freerunner' with 'FreeRunner'</p>
<hr />
<div>== Idea ==<br />
Using bluetooth GPS dongle with any device is in fact nothing more than sending clear text (NMEA protocol) over serial port:<br />
1. BT device (dongle) announces it's serial port (virtual serial port - Bluetooth SPP/SP profile)<br />
2. BT client connects to the dongle<br />
3. Dongle opens serial connection and send stream of NMEA data. That's all!<br />
<br />
'''So let's see what NEO can do:''' <br />
* We got device equipped with GPS<br />
* We got very powerful bluez stack and utilities <br />
* We can get NMEA data<br />
* We can announce Serial (SPP/SP) service using bluetooth<br />
* and finally... we can bind GPS port with BT port and redirect NMEA to any BT client that would like to read it :)<br />
<br />
'''Profits:'''<br />
* We can share GPS data with anyone (Phone/Smartphone/PC/Laptop)<br />
* Maybe sending that data to more than one person (I don't know the exact BT capabilities)<br />
* Whenever you want you can use your PocketPC powered with Automapa or TomTom and don't have to buy another GPS device<br />
* many many more :)<br />
<br />
I've made few tests on desktop debian and was able to get data with Holux GM-101 Handheld GPS (USB Cable) and Nokia N70 (BT)<br />
<br />
<br>'''Holux----(USB)--->Debian-----(BT)---->Nokia'''<br />
<br />
<br />
0. Prerequisites: connect GPS unit, setup bluez and remember to pair your devices!<br />
<br />
1. Make BT listener: '''rfcomm listen 0''' (on my system it binds connected device to /dev/rfcomm0)<br />
<br />
2. Announce your SP service: '''sdptool add sp 1'''<br />
<br />
3. Run some GPS aware application on your client device<br />
<br />
4. On successful connection rfcomm will say something like: <br>''Waiting for connection on channel 1 <br>Connection from 00:**:**:**:**:** to /dev/rfcomm0<br>Press CTRL-C for hangup''<br />
<br />
5. '''cat /dev/ttyUSB0 >/dev/rfcomm0 ''' (where /dev/ttyUSB0 is my USB to serial converter connected to GPS)<br />
<br />
6. Should work :D <br />
<br />
<br />
If you can connect but there is now data:<br />
<br />
- use "cat /dev/your_gps_device" to see if GPS is sending NMEA data to PC (for examle in holux you have to switch some options in menu)<br>should look something like this:<br>'''<br>PGSA,A,2,19,18,,,,,,,,,,,0.0,0.0,0.0*32<br>$GPGSV,3,1,11,03,71,207,23,06,66,169,22,22,64,137,31,19,57,289,32*7F<br>$GPGSV,3,2,11,18,46,065,33,21,21,082,00,16,11,193,00,15,11,025,00*75<br>$GPGSV,3,3,11,08,08,319,00,14,05,142,00,26,05,011,00*44<br>$GPRMC,225506.064,'''<br />
<br />
- check paring <br />
<br />
In a thew weeks time I should get my new Forerunner, so I will try to move this idea to Openmoko platform.<br />
<br />
== FreeRunner as GPS bluetooth device==<br />
This is described here: http://wiki.openmoko.org/wiki/GPS#GTA02<br />
It allows to use the freerunner as ordinary BT GPS reciever. BT aware devices like navigation systems can then use the freeruners GPS signals.<br />
<br />
[[Category:Software ideas]]</div>DolfjeBot1http://openmoko.org/wiki/Wishlist/AccessoriesWishlist/Accessories2008-08-31T13:02:39Z<p>DolfjeBot1: Replacing 'Freerunner' with 'FreeRunner'</p>
<hr />
<div>{{Hardware Wishlist}}<br />
This is a page detailing accessories that may be of use for your Neo1973.<br />
<br />
This is both accessories that do not exist, and existing devices that may be good to add to a web-store.<br />
<br />
Advertising on this page is permitted, but keep it brief and factual.<br />
<br />
=Existing devices=<br />
<br />
==Storage Devices==<br />
<br />
* '''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<br />
<br />
==Input Devices==<br />
<br />
===Pedometer===<br />
<br />
There are (at least) two uses for a Bluetooth pedometer as a Neo1973 accessory:<br />
<br />
* As an input device for exercise-monitoring software<br />
<br />
* 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].)<br />
<br />
=Wishlist=<br />
==Special covers==<br />
Different special covers could be made available with features like:<br />
* A standard slip-on or clip-on template (possibly with buttons) to make the touch-screen blind accessible<br />
* Small metal frame for protection (like Siemens M65, only with more style)<br />
* Case with mirror on the back, for putting on makeup/checking appearance or helping with self-portraits with an integrated camera.<br />
* Option to completely design printable case styles, perhaps with engraving. Ability to share these on a 'community' site.<br />
* Solar powered recharger (perhaps as extendable/unfoldable [[Expansion Back]]).<br />
* Rubber protection like available for iPod, of course in different colors and transparency.<br />
* 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.<br />
* Screen Protector: A simple and very easy to produce screen protector, like the one on my iPaq: <br />
<br />
Protector Flipped up image: http://www.pocketpcthoughts.com/images/ppct-ipaq6900-preview-small-01.jpg<br />
<br />
Protector Flipped down image: http://www.pocketpcthoughts.com/images/ppct-ipaq6900-preview-small-06.jpg<br />
<br />
This serves the dual purpose of protecting the screen from scratches, and stopping user's ear/face from accidentally pressing buttons while talking.<br />
* Scratch-proof protector a la [[InvisibleShield]]<br />
<br />
==Car kit==<br />
A car kit with a cradle which simultaneously recharges the device.<br />
<br />
==Bike kit==<br />
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.<br />
Should also include a padded and waterproof pack that you can place the phone inside, keeping it (somewhat) safe from the elements.<br />
Would also be really cool if it was possible to create a dynamo that can charge the phone, like old school bike headlights.<br />
=== Cadence ===<br />
Something to measure the Cadence like a normal bike computer would be great.<br />
=== Heartbeat ===<br />
Have the possibility to measure the heartbeat would make it a great accessory for training :) <br />
<br />
==Charger conversion connector==<br />
A flexible converter allowing you to recharge the Neo1973 with power from many DC sources such as other devices chargers.<br />
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.<br />
<br />
==Ability to connect a USB keyboard to the phones USB port==<br />
<br />
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.<br />
<br />
<br />
'''Portability'''<br />
<br />
I think it should all be seen within the context of portability.<br />
Have a keyboard incorporated, hinged along the long side, as noted elsewhere, with a micro-switch that induces hibernation on closing to conserve power.<br />
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.<br />
Those of us on the go need a phone, yes, but a lot more.<br />
And all of society is evolving in this direction, so the product needs to also to survive.<br />
<br />
USB2 - obviously, could be employed for something like this:<br />
<br />
[http://www.techpin.com/new-32gb-usb-flash-drives-from-corsair/]<br />
<br />
on which an entire OS with a massive /home partition could be carried round on a keyring.<br />
<br />
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.<br />
<br />
The world needs the portable office, not just the portable phone.<br />
<br />
--<br />
<br />
Weaver.<br />
<br />
==Make the stylus laser-pen recharge its batteries from phone while "docked"==<br />
<br />
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.<br />
<br />
==USB laser pointer==<br />
<br />
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.<br />
<br />
==Bluetooth earpiece with possible both-ears use==<br />
<br />
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.<br />
<br />
Would be nice to have them for the left-handed too.<br />
<br />
==Make a VGA and/or DVI out connector==<br />
<br />
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.<br />
<br />
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.<br />
<br />
== Pouch ==<br />
The pouch could have external or internal place to keep the stylus.<br />
<br />
== USB camera ==<br />
A camera connected to the usb port.<br />
<br />
<br />
<br />
[[Category:Hardware ideas]]</div>DolfjeBot1http://openmoko.org/wiki/Desktop_wallpaper_galleryDesktop wallpaper gallery2008-08-31T13:01:56Z<p>DolfjeBot1: Replacing 'Freerunner' with 'FreeRunner'</p>
<hr />
<div>== Openmoko-inspired wallpaper designs for your desktop systems. ==<br />
<br />
This image helps me design graphics to fit the FreeRunner display, both portrait and landscape, as well as other common display resolutions.<br />
<br />
[[Image:FreeRunnerBlueprint1280x1024.png|640px]]<br />
<br />
----<br />
<br />
Do you have nice openmoko-themed wallpaper? Please share it!<br />
<br />
[[category:User Interfaces]]<br />
[[category:Openmoko]]<br />
[[Category:Add-on data]]</div>DolfjeBot1http://openmoko.org/wiki/VibratorVibrator2008-08-31T13:01:46Z<p>DolfjeBot1: Replacing 'Freerunner' with 'FreeRunner'</p>
<hr />
<div>== Vibrator ==<br />
<br />
This is in reference to the vibrator in the Neo FreeRunner, however it is likely identical to the Neo 1973, as best I can tell.<br />
<br />
=== Controlling ===<br />
The vibrator is controlled through:<br />
/sys/class/leds/neo1973\:vibrator/brightness<br />
When off, it will read 0. Valid ranges appear to be 0-255, with 255 being the fastest.<br />
<br />
=== Vibrate only on Ring ===<br />
<br />
*OM2007.2<br />
The general means of configuring the ringtone is done in the file /etc/pulse/session:<br />
load-sample ringtone /usr/share/openmoko/sounds/ringtone_class.wav<br />
Without that file, the phone will be silent, but still continue to vibrate on ring. A convenient way is to gzip the ringtone file:<br />
gzip /usr/share/openmoko/sounds/ringtone_class.wav<br />
The pulseaudio daemon (or the phone) will need to be restarted:<br />
/etc/init.d/pulseaudio restart<br />
<br />
=== Python Script For Playing Beats ===<br />
Reads beats from a file and plays them on the openmoko vibrator.<br />
<br />
File format is human readable text, consisting of a simple sequence of integer pairs. The first number in the pair representing the intensity of the vibration from 0 to 255. The second number represents the duration in milliseconds to hold that intensity. Any non digit characters in the file count as a separators between numbers, but are otherwise ignored.<br />
<br />
It requires packages python-core and python-re from opkg.<br />
<br />
#!/usr/bin/python<br />
"""Vibrator Beat Player<br />
<br />
Usage: python beatplay.py [filename]<br />
"""<br />
import sys<br />
import time<br />
import re<br />
<br />
def loadFromTextFile(filename):<br />
infile = open(filename)<br />
contents = infile.read()<br />
return re.findall("(\d+)\D*(\d+)", contents)<br />
<br />
def playNote(frequency, duration):<br />
outfile.write(str(frequency) + "\n")<br />
time.sleep(float(duration) / 1000.0)<br />
<br />
def playNotes(notes):<br />
for frequency, duration in notes:<br />
#print frequency + ", " + duration<br />
playNote(frequency, duration)<br />
<br />
def playFile(filename):<br />
global outfile<br />
notes = loadFromTextFile(filename)<br />
outfile = open("/sys/class/leds/neo1973:vibrator/brightness", "w", 1)<br />
playNotes(notes)<br />
playNote(0, 0)<br />
outfile.close()<br />
<br />
if __name__ == "__main__":<br />
playFile(sys.argv[1])<br />
<br />
==== Example Beat ====<br />
The following is an example "song" file that can be used to test the beat player.<br />
<br />
125 400<br />
0 200<br />
250 600<br />
0 400<br />
<br />
125 400<br />
0 200<br />
250 600<br />
0 400<br />
<br />
125 400<br />
0 200<br />
250 600<br />
0 400<br />
<br />
125 400<br />
0 200<br />
250 600<br />
0 400<br />
<br />
[[Category: Hardware]]<br />
[[Category: Vibrator]]</div>DolfjeBot1http://openmoko.org/wiki/Userspace_root_imageUserspace root image2008-08-31T13:01:36Z<p>DolfjeBot1: Replacing 'Freerunner' with 'FreeRunner'</p>
<hr />
<div>== Creating a root filesystem from scratch ==<br />
<br />
To create a root file system image for storage in NAND flash, we use the mkfs.jffs2 program contained in the Debian package ''mtd-tools''.<br />
<br />
mkfs.jffs2 --pad=0x700000 -o rootfs.jffs2 -e 0x4000 -n -d/tmp/jffsroot/<br />
<br />
is a typical command. It creates a FS image for our erase block size of 16k, padded to 0x700000 bytes in length from the files contained in the ''/tmp/jffsroot'' directory and stores the FS image in ''rootfs.jffs2''.<br />
<br />
== Using pre-created rootfs image ==<br />
<br />
=== Prebuilt ===<br />
<br />
See [[Downloads]] and update the list if you have more information.<br />
<br />
=== OpenEmbedded ===<br />
<br />
OpenEmbedded will itself create a jffs2 image at the end of the build process.<br />
<br />
Once the build server is running, it will create root filesystem images for us.<br />
<br />
=== demo JFFS2 root image ===<br />
<br />
Check the [[Flashing openmoko]] page for pre-built root images. Please note that this image may take long to boot the first time, since this boot finishes the installation process.<br />
<br />
=== Mounting the JFFS2 image on a loop back device (Block Memory MTD Emulation) ===<br />
==== Configure the kernel for support ====<br />
For a 2.6.25 kernel:<br />
*Device Drivers<br />
**Block Devices<br />
***Loopback device support<br />
**Memory Technology Device (MTD) support<br />
***Caching block device access to MTD device (mtdblock module, required for block2mtd)<br />
***Self-contained MTD device drivers<br />
****MTD using block device (block2mtd)<br />
*File systems<br />
**Miscellaneous filesystems<br />
***Journalling Flash File System v2 (JFFS2) support<br />
****Advanced compression for JFFS2<br />
*****JFFS2 ZLIB compression support<br />
*****JFFS2 RTIME compressoin support<br />
<br />
==== Mount on loopback device ====<br />
<br />
losetup is an application to manage loop devices, if you have the "losetup -f" option (for instance debian etch do not has such option) you can use the following commands:<br />
<br />
export loop=$(losetup -f)<br />
losetup $loop <rootfs.jffs2><br />
modprobe block2mtd block2mtd=$loop,131072<br />
modprobe jffs2<br />
modprobe mtdblock<br />
mkdir <mountpoint><br />
mount -t jffs2 -o ro /dev/mtdblock0 <mountpoint><br />
<br />
"losetup -f" just returns the first unused loop device, if your system do not comes with "losetup -f" just chose the first /dev/loop* device that is unused and change the first line with:<br />
<br />
export loop=/dev/loop0<br />
<br />
if loop0 is unused <br />
<br />
<br />
Based on this [http://www.internettablettalk.com/forums/showthread.php?p=192475#post192475 script by fanoush].<br />
<br />
The following is an alternate way of doing the above.<br />
modprobe mtdcore<br />
modprobe jffs2<br />
modprobe mtdram total_size=59024 # default is 4 MByte - set to max. available size<br />
modprobe mtdchar<br />
modprobe mtdblock<br />
dd if=<rootfs.jffs2> of=/dev/mtd0<br />
mount -t jffs2 /dev/mtdblock0 <mountpoint><br />
<br />
=== Mounting the JFFS2 image on a loopback device (Kernel Memory MTD Emulation) ===<br />
<br />
As mounting the JFFS2 image from /dev/loop0 device is not supported, use the mtdram device as described in http://www.handhelds.org/hypermail/familiar/62/6232.html<br />
<br />
(On Fedora the first module to load is mtd, not mtdcore and you need to set e.g. vmalloc=256m as a kernel boot parameter for this to work.)<br />
<br />
modprobe mtdcore<br />
modprobe jffs2<br />
modprobe mtdram total_size=59024 # default is 4 MByte - set to max. available size<br />
modprobe mtdchar<br />
modprobe mtdblock<br />
<br />
Using ''total_size=59024'' will set the filesystem size to the available space on /dev/mtd4 of the GTA1 device. So when you copy the image back it will be about 58 MB. You can set this to smaller values though.<br />
<br />
<br />
Be careful to really use the mtd-ram-disk (maybe there is a real Flash-device somewhere in your development system)<br />
<br />
So check for that looking into /proc/mtd:<br />
cat /proc/mtd <br />
# dev: size erasesize name<br />
# mtd0: 039a4000 00020000 "mtdram test device"<br />
<br />
Then write the image to that device and mount it:<br />
<br />
dd if=<rootfs.jffs2> of=/dev/mtd0<br />
mount -t jffs2 /dev/mtdblock0 <mountpoint><br />
<br />
The image is an Little Endian jffs2 image. To mount it on Big Endian architectures (like PowerPC) it'll have to be converted:<br />
<br />
jffs2dump -l -c -e <rootfs.jffs2.be> <rootfs.jffs2> # only needed on non little endian archs<br />
<br />
==== create the new image ====<br />
To get the changed image back there are two ways. The obvious one is to unmount it and copy the data back from the MTD block device (the image will be 58 MB):<br />
<br />
umount /dev/mtdblock0<br />
dd if=/dev/mtdblock0 of=<rootfs.jffs2><br />
<br />
You can also create a new image using the mounted file system and the method described [[Userspace_root_image#Creating_a_root_filesystem_from_scratch | above]] (the image will have the size of its data):<br />
<br />
mkfs.jffs2 --pad=0x700000 -o new_rootfs.jffs2 -e 0x4000 -n -d <mountpoint><br />
<br />
== Flashing a root filesystem into NAND ==<br />
<br />
See [[U-boot#Writing_rootfs_to_NAND]]<br />
<br />
== Converting a GTA02 image for GTA01 ==<br />
<br />
The techniques on this page may be used to convert a GTA02 (FreeRunner) image for use on a GTA01, provided that it is small enough to fit into the GTA01's flash. <br />
<br />
The steps I used are shown below (corrections welcome). Please read all of this page before executing these commands, in particular the warning to make sure that /dev/mtd0 does not map to a real flash device on your system.<br />
<br />
modprobe jffs2<br />
modprobe mtdchar<br />
modprobe mtdblock<br />
modprobe mtdram erase_size=128 total_size=262144<br />
dd if=gta02_image.jffs2 of=/dev/mtd0<br />
mount -t jffs2 -o ro /dev/mtdblock0 /mnt<br />
mkfs.jffs2 --little-endian -e 16 -x lzo --pad -n -r /mnt -o for_gta01.jffs2<br />
<br />
To clean up when you're done:<br />
umount /mnt<br />
rmmod mtdram<br />
<br />
<br />
{{Languages|Userspace_root_image}}<br />
[[Category:Openmoko]]<br />
[[Category:Guides]]</div>DolfjeBot1http://openmoko.org/wiki/USB_hostUSB host2008-08-31T13:01:26Z<p>DolfjeBot1: Replacing 'Freerunner' with 'FreeRunner'</p>
<hr />
<div>== USB host ==<br />
The mini-USB port on both the Neo 1973 and the Neo FreeRunner supports both USB host and USB device. This opens up a range of possibilities, such as adding USB cameras and USB input devices.<br />
<br />
=== Selecting USB host mode ===<br />
<br />
By default, the mini-USB port is in device mode. To tell the Neo that it is logically a host:<br />
<br />
echo "host" > /sys/devices/platform/s3c2410-ohci/usb_mode<br />
<br />
Independent of the logical mode of the USB port, the Neo FreeRunner can provide 5 volt USB power to an attached USB device. To enable this (not available on Neo 1973):<br />
<br />
echo "1" > /sys/devices/platform/neo1973-pm-host.0/hostmode<br />
<br />
Note: You may want to run <code>ifconfig usb0 down</code> prior to switching to USB host mode, as the Neo's USB networking may not like having its USB port disappear. You'll probably want to ssh into your Neo over WiFi or Bluetooth before starting all of this, alternatively use an on screen keyboard.<br />
<br />
=== Providing power to connected USB devices while in host mode ===<br />
<br />
Normally, USB host ports provide power to any connected USB device.<br />
<br />
Available power in host mode is the full maximum of 500mA according to USB-specifications on the Neo FreeRunner, and no power is available in host mode on the Neo 1973. If your USB device respects USB-standards and consumes not more than 500mA, you may connect it directly to your Neo FreeRunner.<br />
<br />
To provide power to USB devices attached to your Neo 1973, or to provide power to your Neo FreeRunner while USB-device connected, you can provide power by using a (modified [for powering FreeRunner]) powered USB hub (see below), or by manually injecting power into the attached USB device (and Neo FreeRunner) via one of the [[specialized_USB_cables]].<br />
<br />
=== Powered USB hubs known to work with the Neo ===<br />
<br />
(please add any known to work)<br />
<br />
=== Providing power to run and charge the Neo while in host mode ===<br />
<br />
A slightly separate issue is power to run and charge the Neo (both types) itself. When the USB port is in device mode, the Neo FreeRunner/1973 can be powered and recharged via the USB port, but when in standard host mode, the Neo FreeRunner is set to provide power and does not charge. Fortunately, control of the direction of power (in or out) is independent of the personality of the USB port (host or device):<br />
<br />
To recap, the direction of power can be controlled:<br />
<br />
Set to 0 (default), no power is provided at the USB port, charging is enabled, and host 15K pulldowns are removed from D+ and D-:<br />
<br />
echo "0" > /sys/devices/platform/neo1973-pm-host.0/hostmode<br />
<br />
Set to 1, provides up to 500mA USB power at the USB port (FreeRunner only), disables charging from USB, and applies 15K pulldowns to USB D+ and D-:<br />
<br />
echo "1" > /sys/devices/platform/neo1973-pm-host.0/hostmode<br />
<br />
Next, power must somehow be injected. An unmodified powered USB hub only provides power to the connected devices, but not to the connected host, so the only solution here is to modify a USB-hub¹) or to create a custom cable which will inject power into the host. See [[specialized_USB_cables]] for some examples.<br />
<br />
Finally, there is the question of charge rate. The charging logic in the Neo will only charge at 100mA by default. Charging at 500mA will take place only if the charging device responds appropriatly to USB negotiation to increase power consumption. Charging at 1000mA will only take place if the Neo detects the appropriate resistor on the ID pins.<br />
<br />
You can manually set the charge rate. See [[Forcing_fast_charge_mode]]<br />
<br />
¹) often it's sufficient to short a diode in USB-hub to feed power to the host-connector too.<br />
<br />
<br />
<br />
=== Power Concerns ===<br />
You'll need to force the Neo to go into fast charge mode, since it can't do its usual power negotiation over USB.<br />
<br />
echo -n "fast_cccv" > /sys/devices/platform/s3c2410-i2c/i2c-adapter/i2c-0/0-0008/chgmode<br />
<br />
(Also this should be done by kernel when seeing 47K at ID-pin)<br />
<br />
[[Category:Neo1973 Hardware]]<br />
[[Category:Neo FreeRunner Hardware]]<br />
[[Category:USB]]</div>DolfjeBot1http://openmoko.org/wiki/Neo_USB_charger_specifications_and_compatibility_listNeo USB charger specifications and compatibility list2008-08-31T13:01:17Z<p>DolfjeBot1: Replacing 'Freerunner' with 'FreeRunner'</p>
<hr />
<div>{{Languages|USB charger}}<br />
<br />
The [[Neo FreeRunner]] and the [[Neo 1973]] can be charged with the supplied USB charger, which is a device that does not comply with the recent [http://www.usb.org/developers/devclass_docs/batt_charging_1_0.zip USB Battery Charging Specification]. This specification demands for an open circuit on the ID pin and a short circuit between the D+ and D- pins.<br />
<br />
Most of the USB chargers around behave the same way as the one supplied with the Openmoko Neo. In fact, up to now no charger has been identified to comply to the specification mentioned above. The differences (incompatibilities) result from the way the USB charger signals the mobile phone that it is present: most of the manufacturers chose to connect a resistor between the "ID" pin and the "GND" pin in the USB connector.<br />
<br />
For Openmoko Neo, the value of the resistor is 47.5 kOhms.<br />
<br />
Additional details can be found at : http://quickstart.openmoko.org/#chargerdetection<br />
<br />
Following USB chargers have been identified and measured:<br />
<br />
== AKII Technology Charger (supplied with Neo FreeRunner) ==<br />
<br />
This charger comes with the Neo FreeRunner package.<br />
<br />
=== Specifications ===<br />
<br />
*Model: [http://www.ak2.com.tw/pd_main.asp?sg_id=11 A10P1-05MP]<br />
*Input: 100-240V~ /0.3A<br />
*Output: +5v up to 2.0A<br />
*Signaling: 47.5k 1% resistor between ID pin and ground for openmoko charger identification<br />
<br />
=== Compatibility ===<br />
<br />
*HTC Polaris (tested on O2 Xda Orbit 2)<br />
*Openmoko Neo1973<br />
*Openmoko Neo FreeRunner<br />
<br />
== Blackberry PSM05R-050CHW ==<br />
[[Image:P1040112.jpg|thumb|300px]]<br />
<br />
=== Specifications ===<br />
<br />
*Model: PSM05R-050CHW<br />
*Output: DC 5 V - 0.5 A<br />
<br />
=== Compatibility ===<br />
<br />
*Openmoko Neo FreeRunner, provided the 500 mA charging mode is enabled on the FR (see [[Forcing_fast_charge_mode]]), as otherwise it would only (dis)charge, as the FR would only draw 100 mA out of it.<br />
<br />
== ''sold as'' "Essentiel b (Boulanger)" ''Chargeur allume-cigares/USB'' ==<br />
[[Image:P1040105.jpg|thumb|300px]]<br />
This car charger is sold at the French appliances superstore ''Boulanger'' but should be available in other stores under different brands. It is an adapter to a USB cable which can then be connected to any USB-charging device. By default, it will be seen as a "passive" USB port at 100 mA.<br />
<br />
=== Specifications ===<br />
<br />
*Model: Cod. 779220<br />
*Input: DC 12-30 V<br />
*Output: DC 5 V - 850 mA max<br />
<br />
=== Compatibility ===<br />
<br />
*Openmoko Neo FreeRunner, provided the 500 mA charging mode is enabled on the FR (see [[Forcing_fast_charge_mode]]), as otherwise it would only (dis)charge, as the FR would only draw 100 mA out of it.<br />
<br />
== Garmin 362-00043-04 ==<br />
[[Image:Charger_garmin.jpg|thumb|300px|Garmin 362-00043-04]]<br />
This charger comes with the Garmin Edge bicycle computers.<br />
<br />
=== Specifications ===<br />
*Manufacturer: probably Phihong Technology Co., Ltd.<br />
*Model: PSCR05R-050A1<br />
*Input: 100-240V~ 0.2A 50-60Hz<br />
*Output: 5V up to 1.0A<br />
*Signaling: D+ and D- open, 17.4 kOhms resistor between ID pin and ground pin<br />
<br />
=== Compatibility ===<br />
*Garmin Edge<br />
*HTC Polaris (tested on O2 Xda Orbit 2)<br />
<br />
<br />
== HTC 79H00051-02M ==<br />
This charger comes with the tmobile MDA Compact 2 (HTC Charmer).<br />
=== Specifications ===<br />
*Manufacturer: Delta Electronics Inc.<br />
*Model: ADP-5FH C<br />
*Input: 100-240V~ 0.2A 50-60Hz<br />
*Output: 5V= 1.0A LPS<br />
*Signaling: D+ and D- open, short circuit between ID pin and ground pin<br />
<br />
=== Compatibility ===<br />
*HTC Charmer (tested on MDA Compact 2)<br />
*Openmoko Neo FreeRunner<br />
<br />
<br />
== HTC 79H00055-02M ==<br />
[[Image:Charger_htc.jpg|thumb|300px|HTC 79H00055-02M]]<br />
This charger comes with the O2 Xda Orbit 2 (HTC Polaris).<br />
=== Specifications ===<br />
*Manufacturer: Phihong Technology Co., Ltd.<br />
*Model: PSAA05E-050 (the letter E denotes the EU power connector. There are also US, UK and AUS variants of this model)<br />
*Input: 100-240V~ 0.3A<br />
*Output: 5.15V up to 1.0A (over-current protection at 2A)<br />
*Signaling: D+ and D- open, short circuit between ID pin and ground pin<br />
<br />
=== Compatibility ===<br />
*HTC Polaris (tested on O2 Xda Orbit 2)<br />
*Garmin Edge<br />
<br />
<br />
== PHIHONG CLM10D-050 ==<br />
[[Image:Charger__htc_12V.jpg|thumb|300px|PHIHONG CLM10D-050]]<br />
This 12V cigarette lighter adapter charger comes with the O2 Xda Orbit 2 (HTC Polaris).<br />
=== Specifications ===<br />
*Manufacturer: Phihong Technology Co., Ltd.<br />
*Model: CLM10D-050<br />
*Input: 10-30V DC<br />
*Output: 5.0V up to 2.0A<br />
*Signaling: D+ and D- open, short circuit between ID pin and ground pin<br />
<br />
=== Compatibility ===<br />
*HTC Polaris (tested on O2 Xda Orbit 2)<br />
*Garmin Edge<br />
<br />
[[Category:Hardware]]<br />
[[Category:Neo1973 Hardware]]<br />
[[Category:Neo FreeRunner Hardware]]<br />
[[Category:Battery]]<br />
[[Category:USB]]</div>DolfjeBot1http://openmoko.org/wiki/USB_Networking_with_openSUSEUSB Networking with openSUSE2008-08-31T13:01:06Z<p>DolfjeBot1: Replacing 'Freerunner' with 'FreeRunner'</p>
<hr />
<div>= YaST in openSUSE 10.1 & 10.2 =<br />
<br />
== Set up USB interface ==<br />
<br />
First, you must specify the characteristics of the USB connection as a network device. This can be done through YaST. Choose:<br />
<br />
YaST -> Network Devices -> Network Card<br />
<br />
The network configuration utility will ask you to choose between a setup based on the Network Manager app, or by using ifup. These instructions were written with the latter chosen, though it may very well work using the Network Manager. In the next menu, you will see a list of network devices. If YaST recognizes the connected FreeRunner, there will be one device with a name like "RNDIS ethernet gadget". You may select "Edit" to configure this device, or, if it is not present, "Add" it and continue.<br />
<br />
In the "Edit" dialog, under the <i>Address</i> tab, choose "Static Address Setup" and set:<br />
<br />
IP Address = 192.168.0.200<br />
<br />
and<br />
<br />
Subnet Mask = 255.255.255.0<br />
<br />
<b>Note:</b> If your network setup has the IP range 192.168.0.x already in use, there will be connectivity problems. Next, under the <i>General</i> tab for this device, set:<br />
<br />
Firewall Zone -> Internal Zone (Unprotected)<br />
<br />
This will allow for the configuration of the firewall, which comes later. Click "Next" to finish configuring this device. (Your primary network device, usually eth0, may be set to use DHCP for addressing, but must have its firewall zone set to "External Zone".) Choose "Finish" in the Configuration Overview to complete the setup and restart networking.<br />
<br />
== Enable IP Forwarding ==<br />
<br />
To use your host PC as a router for the FreeRunner, you must implement IP forwarding. This is also done in YaST:<br />
<br />
YaST -> Network Services -> Routing<br />
<br />
At the bottom of the dialog, enable "IP Forwarding"; no default gateway is necessary. Choose "Finish" to end routing configuration.<br />
<br />
== Configure Firewall ==<br />
<br />
The firewall must be configured to allow traffic to and from the FreeRunner. Start by:<br />
<br />
YaST -> Security and Users -> Firewall<br />
<br />
(1) Under the <i>Interfaces</i> tab, confirm that the network device that connects to the internet is in the "External Zone" and the USB device is in the "Internal Zone". (2) In the <i>Allowed Services</i> tab, there is a checkbox labeled "Protect Firewall from Internal Zone". Uncheck it. (3) In the <i>Masquerading</i> tab, check the "Masquerade Networks" box. (4) Clicking "Next" will get to a firewall summary dialog, then clicking "Accept" will configure and restart the firewall.<br />
<br />
== Configure NAT ==<br />
<br />
After configuring and starting the USB interface, engaging the host PC as a router, and opening the firewall. You may add a route to the FreeRunner and start network address translation (NAT). It may be best to write short scripts to perform these actions, so they may be invoked without remembering or typing them. In one script, <b>neoFRup.sh</b>, place the commands:<br />
<br />
#! /bin/sh<br />
/sbin/route add -host 192.168.0.202/32 dev usb0<br />
iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24<br />
iptables -P FORWARD ACCEPT<br />
<br />
This script will add the FreeRunner to the route tables and enable NAT, so you should now be able to connect to your phone with:<br />
<br />
# ssh root@192.168.0.202<br />
<br />
You should make sure that there is a gateway set to 192.168.0.200 in the FR's /etc/network/interfaces file, and that the FR's /etc/resolv.conf file has appropriate nameservers listed. When you are finished using the route to your phone, you may undo the above with another script, <b>neoFRdown.sh</b>:<br />
<br />
#! /bin/sh<br />
/sbin/route del -host 192.168.0.202/32 dev usb0<br />
iptables -t nat -F POSTROUTING<br />
<br />
[[category:Technical]]<br />
[[category:USB]]</div>DolfjeBot1http://openmoko.org/wiki/USB_NetworkingUSB Networking2008-08-31T13:00:57Z<p>DolfjeBot1: Replacing 'Freerunner' with 'FreeRunner'</p>
<hr />
<div>= Openmoko Networking Setup =<br />
<br />
In order to communicate via TCP/IP to your FreeRunner, a basic understanding of the networking expectations is required. Each end of the USB connection forms a LAN (local area network) segment, with the FreeRunner's USB networking device at one end (default 192.168.0.202) and your laptop or desktop at the other end (192.168.0.200 in this guide).<br />
<br />
Normally, your desktop machine will know how to reach the Internet, having had its gateway (the IP address of the machine or device which knows how to send packets to machines beyond your subnet) configured via DHCP or statically (probably via a router). For the FreeRunner to reach the Internet, your desktop will have to be configured to route and masquerade (NAT) packets from it. <br />
<br />
Normally, none of this is an issue, but problems can arise when the subnet between the FreeRunner and your desktop overlap with the desktop to the router (which forms a second LAN), since your desktop might not know how to route traffic properly.<br />
<br />
In other words: if your existing router and desktop have addresses 192.168.0.(something) changing them to eg 192.168.1.(something) might save you a lot of troubleshooting later. The guides to set up USB networking for your FreeRunner assume that your router/desktop IP range differs from the USB network IP range.<br />
<br />
A discussion of this is here http://lists.openmoko.org/pipermail/support/2008-August/001283.html<br />
<br />
= Simple Manual Linux Configuration =<br />
<br />
Try this first. If it works, then you can add permanent configuration or use more sophisticated setups below:<br />
<br />
(as root on your desktop):<br />
<br />
iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24<br />
sysctl -w net.ipv4.ip_forward=1<br />
ifconfig usb0 192.168.0.200<br />
<br />
If your Internet connection is also in the range 192.168.0.x then instead you might want to use:<br />
<br />
ifconfig usb0 192.168.0.200 netmask 255.255.255.248<br />
<br />
Then (ideally, not as root):<br />
<br />
ssh root@192.168.0.202<br />
<br />
The default password is blank.<br />
<br />
= Linux Kernel Support =<br />
<br />
Your Linux desktop/laptop needs to have suitable support, in particular, you will need to have enabled full masquerading in the kernel and USB networking options enabled. For default kernels in many Linux distributions, this will already be the case. If not, you will need to enable:<br />
<br />
* CONFIG_USB_USBNET<br />
* CONFIG_USB_NET_CDCETHER<br />
<br />
Both USB networking options are available in the <br />
<br />
''Device Drivers -> USB support -> USB Network Adapters'' <br />
<br />
or <br />
<br />
''Device Drivers -> Network Device Support -> USB Network Adapters -> Multipurpose USB Networking Framework''. <br />
<br />
For more info see the [http://www.linux-usb.org/usbnet/ usbnet driver homepage].<br />
<br />
It can be complex to set all the correct options for masquerading in the kernel if they are not turned on. This could be detailed further.<br />
<br />
= Firewall Issues =<br />
<br />
On some systems, you may have firewall rules which prevent this working - such as added by the iptables service on Fedora. You may care to stop these, and/or review any rules or policies you think might cause issues.<br />
<br />
The most relevant table is the nat table, which controls translation of addresses:<br />
<br />
iptables -L -t nat -v -n<br />
<br />
Unless you have a special setup, you'll want to see only the MASQUERADE rule that you apply below, and ACCEPT as the default policy. Also look at the filter table:<br />
<br />
iptables -L -t filter -v -n<br />
<br />
If this contains anything in the FORWARD chain, then this may prevent passing packets. It can be flushed with:<br />
<br />
iptables -t filter -F FORWARD<br />
<br />
= DNS =<br />
<br />
In addition to routing issues, to be practical, DNS will need to work. In some cases, you might already be running a DNS server on your desktop such as dnsmasq or bind9, which is the default assumption the FreeRunner makes. In other cases, you'll need to configure DNS to that of your router, or a DNS server further out on the internet such as that provided by your ISP.<br />
<br />
== Configure Default Neo DNS ==<br />
<br />
DNS is configured in /etc/resolv.conf on your FreeRunner. <br />
<br />
You should add the IP address of the DNS servers as provided by your ISP. Check your router's or PC's network status for the nameserver IP addresses.<br />
<br />
echo nameserver xxx.xxx.xxx.xxx > /etc/resolv.conf<br />
<br />
You can also add the public DNS server called openDNS:<br />
echo nameserver 208.67.222.222 > /etc/resolv.conf<br />
echo nameserver 208.67.220.220 >> /etc/resolv.conf<br />
<br />
These settings will be lost on reboot. You can set the DNS for the next connect, by adding the following to the end of the usb0 setting in /etc/network/interfaces, right above the bluetooth networking section:<br />
up echo nameserver 208.67.222.222 > /etc/resolv.conf<br />
up echo nameserver 208.67.220.220 >> /etc/resolv.conf<br />
<br />
== Proxying DNS from Desktop/Laptop ==<br />
<br />
If you move about, making assumptions about the network may not be convenient, and it is possible to proxy DNS requests via your host laptop (which you are also taking with you), without running or installing a DNS server. There are a number of ways to do this:<br />
<br />
=== Proxying with dnrd ===<br />
<br />
The script is designed to use [http://dnrd.sourceforge.net/ dnrd] as the DNS proxy. The [http://buildhost.automated.it/gta01 script] and a copy of [http://buildhost.automated.it/dnrd-2.20.3.tar.gz dnrd] are available. The script also performs the initial setup of the connection as per the [[USB_Networking#Manual_method]] above.<br />
<br />
=== Proxying with a UDP forwarder ===<br />
<br />
Another easy setup is using a UDP forwarder like the one from http://www.tapor.com/udpf/ - use it with the command"<br />
<br />
udpf-elf -p=53-f=`cat /etc/resolv.conf|awk '$1 == "nameserver"{print $2; exit(0);}'`:53<br />
<br />
=== Proxying with iptables ===<br />
<br />
It is possible to forward DNS requests with iptables using the DNAT target:<br />
<br />
iptables -t nat -A PREROUTING -p tcp -s 192.168.0.202 -d 192.168.0.200 --dport domain -j DNAT --to-destination 192.168.0.1<br />
iptables -t nat -A PREROUTING -p udp -s 192.168.0.202 -d 192.168.0.200 --dport domain -j DNAT --to-destination 192.168.0.1<br />
<br />
Where <tt>192.168.0.1</tt> is the IP of your router.<br />
<br />
Test if it works:<br />
ping www.google.com<br />
<br />
If so, then this is sufficient for most internet access. But manual changes to resolv.conf are usually lost later if for example one uses DHCP, especially for WiFi, and so may not be convenient to configure manually.<br />
<br />
= Testing Your Connection =<br />
You should be able to connect to your Neo! Make sure you can ping your Neo to be sure.<br />
ping 192.168.0.202<br />
<br />
Then log into your Neo using ssh:<br />
ssh root@192.168.0.202<br />
The default password is blank (press enter).<br />
<br />
You can also [[scp]] files back and forth. 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.<br />
<br />
Now, make sure you can ping back to your desktop<br />
ping 192.168.0.200<br />
(Note that some systems like Vista, don't respond to ICMP ping by default) <br />
<br />
Try pinging the outside world (a Google IP address)<br />
ping 74.125.19.147<br />
This demonstrates that masquerading is working - your desktop is sending/receiving packets to the wider internet.<br />
<br />
Lastly, verify that DNS is correctly configured between the Neo & Network:<br />
ping www.google.com<br />
<br />
= OS or Distro Specific & Automatic Configuration =<br />
<br />
Based on [http://blog.haerwu.biz/2007/03/22/hotpluging-usbnet/ Hotplugging usbnet] by Marcin 'Hrw' Juszkiewicz.<br />
These instructions should keep you from having to run the Simple Manual Linux Configuration every time you plug in and want to connect to an Openmoko device. One run and then you're done!<br />
<br />
If the Simple Manual Linux Configuration does not work for your OS or Distro (MacOS X, MS Windows, etc) there may be instructions here that work for you. <br />
<br />
== MacOS X ==<br />
See [[MacOS_X#USB_Networking|MacOS X USB Networking]].<br />
<br />
== Windows ==<br />
See [[Neo1973_and_Windows#USB_Ethernet_emulation|Windows USB Ethernet emulation for Neo1973]].<br />
<br />
== FreeBSD ==<br />
You need to load the cdce kernel module.<br />
As root do:<br />
<br />
kldload cdce<br />
<br />
The Neo should then show up as cdce0 and you can handle the cdce0 device just like the usb0 device under Linux. For more information see the cdce manpage.<br />
<br />
== Debian, Ubuntu and others ==<br />
<br />
Edit /etc/network/interfaces and add:<br />
<br />
<pre><br />
auto usb0<br />
iface usb0 inet static<br />
address 192.168.0.200<br />
netmask 255.255.255.0<br />
network 192.168.0.0<br />
up iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24 &<br />
up echo 1 > /proc/sys/net/ipv4/ip_forward &<br />
up iptables -P FORWARD ACCEPT &<br />
down iptables -D POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24 &<br />
<br />
</pre><br />
<br />
This is more sophisticated than the manual setup. The 'auto usb' stanza ties into the Linux hotplug system so that when the device appears and vanishes, as happens when the FreeRunner is connected via USB, this is run. <br />
<br />
In addition, the desktop-side netmask is limited to a much smaller range, so that overlapping subnets are less of a problem - Linux will use more specific routes first when deciding where to send packets.<br />
<br />
Another possible configuration that adds DNS forward and removes<br />
the iptables changes after unplugging:<br />
<br />
in /etc/network/interfaces add<br />
<pre><br />
# freerunner<br />
auto usb0<br />
iface usb0 inet static<br />
address 192.168.0.200<br />
netmask 255.255.255.192<br />
post-up /etc/network/freerunner start<br />
pre-down /etc/network/freerunner stop<br />
</pre><br />
<br />
create file /etc/network/freerunner<br />
<pre><br />
#!/bin/sh<br />
#<br />
# configures the freerunner for internet<br />
# <br />
# <br />
<br />
DEVICE=usb0<br />
IPADDR=192.168.0.200<br />
REMOTE_IPADDR=192.168.0.202<br />
NETMASK=255.255.255.0<br />
<br />
# get first ip for dns<br />
DNSIP=$(cat /etc/resolv.conf | grep nameserver | awk '{ print $2 }' | head -n 1 )<br />
<br />
case "$1" in<br />
start)<br />
iptables -A POSTROUTING -t nat -j MASQUERADE -s $REMOTE_IPADDR<br />
iptables -A PREROUTING -t nat -p tcp -s $REMOTE_IPADDR -d $IPADDR --dport domain -j DNAT --to-destination $DNSIP<br />
iptables -A PREROUTING -t nat -p udp -s $REMOTE_IPADDR -d $IPADDR --dport domain -j DNAT --to-destination $DNSIP<br />
<br />
if [ "$(cat /proc/sys/net/ipv4/ip_forward)" = "0" ]; then<br />
echo "temoprarely allow ip_forward for openmoko" > /var/run/openmoko.ip_forward<br />
echo 1 > /proc/sys/net/ipv4/ip_forward<br />
fi<br />
;;<br />
stop)<br />
iptables -D POSTROUTING -t nat -j MASQUERADE -s $REMOTE_IPADDR<br />
iptables -D PREROUTING -t nat -p tcp -s $REMOTE_IPADDR -d $IPADDR --dport domain -j DNAT --to-destination $DNSIP<br />
iptables -D PREROUTING -t nat -p udp -s $REMOTE_IPADDR -d $IPADDR --dport domain -j DNAT --to-destination $DNSIP<br />
<br />
if [ -f /var/run/openmoko.ip_forward ]; then<br />
rm /var/run/openmoko.ip_forward<br />
echo 0 > /proc/sys/net/ipv4/ip_forward<br />
fi<br />
;;<br />
esac<br />
</pre><br />
<br />
Make /etc/network/freerunner executable with <br />
chmod +x /etc/network/freerunner<br />
<br />
=== Ubuntu Issues ===<br />
<br />
Ubuntu Feisty, Gutsy and Hardy reportedly have a bug where ifdown is not run when the interface is unplugged, meaning this only works once after the system is booted. This is mentioned at https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/130437 <br />
<br />
One can patch /etc/udev/rules.d/85-ifupdown.rules, editing the two lines at the end of the file:<br />
<br />
SUBSYSTEM=="net", DRIVERS=="?*", GOTO="net_start"<br />
GOTO="net_end"<br />
<br />
LABEL="net_start"<br />
<br />
# Bring devices up and down only if they're marked auto.<br />
# Use start-stop-daemon so we don't wait on dhcp<br />
ACTION=="add", RUN+="/sbin/start-stop-daemon --start --background --pidfile /var/run/network/bogus --startas /sbin/ifup -- --allow auto $env{INTERFACE}"<br />
<br />
LABEL="net_end"<br />
<br />
ACTION=="remove", RUN+="/sbin/start-stop-daemon --start --background --pidfile /var/run/network/bogus --startas /sbin/ifdown -- --allow auto $env{INTERFACE}"<br />
<br />
The bug is that the LABEL="net_end" is at the wrong position<br />
<br />
<br />
This appears to be fixed in Ubuntu 8.04 [[User:Mattt|Mattt]] 11:38, 30 July 2008 (UTC)<br />
:Actually it appears that it's not fixed, but patching that file and disconnecting and reconnecting the phone works perfectly. --[[User:Johndoesacc|Johndoesacc]] 18:37, 20 August 2008 (UTC)<br />
<br />
== Mandriva ==<br />
<br />
Tested with Mandriva 2008.1. The idea here is that we will carve out a small (8 hosts) subnet from the main subnet. So our netmask will be 255.255.255.252<br />
<br />
This first file configures the network system for the usb0 interface. Any time you plug in the FreeRunner the interface will be configured. <br />
<br />
/etc/sysconfig/network-scripts/ifcfg-usb0:<br />
<br />
DEVICE=usb0<br />
BOOTPROTO=static<br />
IPADDR=192.168.0.200<br />
NETMASK=255.255.255.252<br />
ONBOOT=yes<br />
METRIC=10<br />
MII_NOT_SUPPORTED=no<br />
USERCTL=yes<br />
<br />
This next file configures the static routes that we need to communicate to the subnet. Since it has "usb0" in the name, the system will automatically apply these static routes any time that the usb0 interface is configured. (i.e. when you connect the FreeRunner)<br />
<br />
/etc/sysconfig/network-scripts/usb0-routes:<br />
<br />
ADDRESS0=192.168.0.200<br />
NETMASK0=255.255.255.252<br />
<br />
Now we need to restart the network system to pick up the changes.<br />
<br />
service network restart<br />
<br />
== SuSE ==<br />
<br />
/etc/sysconfig/network/ifcfg-usb0:<br />
<br />
# USB configuration for PDAs (openmoko)<br />
IPADDR=192.168.0.200<br />
NETMASK=255.255.255.0<br />
STARTMODE=onboot<br />
<br />
For more information on getting USB networking up using YaST, see [[USB Networking with openSUSE]].<br />
<br />
== Fedora ==<br />
<br />
=== Option A - Tested with FC8 & FC5 ===<br />
<br />
/etc/sysconfig/network-scripts/ifcfg-usb0:<br />
<br />
# USB configuration for PDAs (openmoko)<br />
# from http://www.handhelds.org/moin/moin.cgi/UsbNet<br />
DEVICE=usb0<br />
BOOTPROTO=none<br />
IPADDR=192.168.0.200<br />
NETMASK=255.255.255.0<br />
ONBOOT=yes<br />
<br />
=== Option B ===<br />
<br />
This setup is probably over-complex:<br />
<br />
/etc/sysconfig/network-scripts/ifcfg-usb0:<br />
<br />
DEVICE=usb0<br />
IPADDR=192.168.0.200<br />
NETMASK=255.255.255.0<br />
<br />
/etc/sysconfig/network-scripts/ifup-usb:<br />
<br />
#!/bin/bash<br />
<br />
. /etc/init.d/functions<br />
<br />
cd /etc/sysconfig/network-scripts<br />
. ./network-functions<br />
<br />
[ -f ../network ] && . ../network<br />
<br />
CONFIG=${1}<br />
<br />
need_config ${CONFIG}<br />
<br />
source_config<br />
<br />
NETBITS=`ipcalc -p ${IPADDR} ${NETMASK} | awk -F'=' '{print $2;}'`<br />
<br />
/sbin/ip addr flush dev ${DEVICE} 2>/dev/null<br />
/sbin/ip link set dev ${DEVICE} up<br />
/sbin/ip addr add dev ${DEVICE} ${IPADDR}/${NETBITS}<br />
<br />
/sbin/iptables -I POSTROUTING -t nat -j MASQUERADE -s ${IPADDR}/${NETBITS}<br />
/sbin/sysctl net.ipv4.ip_forward=1<br />
/sbin/iptables -I FORWARD -s ${IPADDR}/${NETBITS} -j ACCEPT<br />
/sbin/iptables -I FORWARD -d ${IPADDR}/${NETBITS} -j ACCEPT<br />
<br />
Set /etc/sysconfig/network-scripts/ifdown-usb:<br />
<br />
#!/bin/bash<br />
<br />
. /etc/init.d/functions<br />
<br />
cd /etc/sysconfig/network-scripts<br />
. ./network-functions<br />
<br />
[ -f ../network ] && . ../network<br />
<br />
CONFIG=${1}<br />
<br />
need_config ${CONFIG}<br />
<br />
source_config<br />
<br />
NETBITS=`ipcalc -p ${IPADDR} ${NETMASK} | awk -F'=' '{print $2;}'`<br />
<br />
/sbin/iptables -D FORWARD -d ${IPADDR}/${NETBITS} -j ACCEPT<br />
/sbin/iptables -D FORWARD -s ${IPADDR}/${NETBITS} -j ACCEPT<br />
/sbin/sysctl net.ipv4.ip_forward=0<br />
/sbin/iptables -D POSTROUTING -t nat -j MASQUERADE -s ${IPADDR}/${NETBITS}<br />
<br />
/sbin/ip link set dev ${DEVICE} down<br />
/sbin/ip addr flush dev ${DEVICE} 2>/dev/null<br />
<br />
If you are using NetworkManager, restart it and enable the usb device from its menu, otherwise it will disable your connection shortly after you enable it.<br />
<br />
/sbin/service NetworkManager restart<br />
<br />
== Red Hat or Similar (tested with Workstation 5) ==<br />
<br />
Edit /etc/sysconfig/network-scripts/net.hotplug:<br />
<br />
After this command:<br />
<br />
<pre><br />
case $INTERFACE in<br />
# interfaces that are registered after being "up" (?)<br />
</pre><br />
<br />
add<br />
<br />
<pre><br />
usb0)<br />
ifconfig usb0 192.168.0.200 netmask 255.255.255.0<br />
route add 192.168.0.202 usb0<br />
iptables -I INPUT 1 -s 192.168.0.202 -j ACCEPT<br />
iptables -I OUTPUT 1 -s 192.168.0.200 -j ACCEPT<br />
iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24<br />
echo 1 > /proc/sys/net/ipv4/ip_forward<br />
exit 0<br />
;;<br />
</pre><br />
<br />
== Gentoo ==<br />
<br />
Open /etc/conf.d/net and add:<br />
<br />
# Neo<br />
config_usb0=( "192.168.0.200 netmask 255.255.255.0" )<br />
routes_usb0=( "192.168.0.202/32 via 192.168.0.200" )<br />
<br />
Create a new init script:<br />
<br />
cd /etc/init.d<br />
ln -s net.lo net.usb0<br />
<br />
Put iptables into use:<br />
<br />
iptables -I INPUT 1 -s 192.168.0.202 -j ACCEPT<br />
iptables -I OUTPUT 1 -s 192.168.0.200 -j ACCEPT<br />
iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24<br />
<br />
Store them:<br />
<br />
/etc/init.d/iptables save<br />
<br />
If you want the routing by default:<br />
<br />
rc-update add iptables default<br />
<br />
You must also inform the kernel, to start forwarding. <br />
<br />
echo 1 > /proc/sys/net/ipv4/ip_forward<br />
<br />
One way to automate all this is to create /etc/conf.d/net.usb0 as follows. It sets IP forwarding and the iptables rules all in one go. It removes the iptables rules and disables ip forwarding when the FreeRunner is unplugged.<br />
<br />
preup() {<br />
echo 1 > /proc/sys/net/ipv4/ip_forward<br />
iptables -I INPUT 1 -s 192.168.0.202 -j ACCEPT<br />
iptables -I OUTPUT 1 -s 192.168.0.200 -j ACCEPT<br />
iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24<br />
return 0<br />
}<br />
<br />
postdown() {<br />
echo 0 > /proc/sys/net/ipv4/ip_forward<br />
iptables -D INPUT -s 192.168.0.202 -j ACCEPT<br />
iptables -D OUTPUT -s 192.168.0.200 -j ACCEPT<br />
iptables -D POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24<br />
return 0<br />
}<br />
<br />
= SSH Extras =<br />
<br />
Reportedly, the ssh daemon (dropbear 0.49) on the FreeRunner 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.<br />
<br />
To avoid ssh adding a new line for every ssh host-key to your known_hosts you can add the following to the phone section in ~/.ssh/config<br />
<br />
UserKnownHostsFile /dev/null<br />
<br />
You might want to use keys to bypass the login prompt too.<br />
<br />
== SSH Keys ==<br />
<br />
== From desktop to FreeRunner ==<br />
<br />
To generate ssh keys for use as a login mechanism type:<br />
<br />
ssh-keygen -t rsa<br />
<br />
When prompted for a password either hit enter for no password (''not really a good idea'') or enter a password for this key. ssh into the phone and create ~/.ssh:<br />
<br />
# mkdir ~/.ssh<br />
<br />
Then from your desktop copy the '''.pub''' file to the phone.<br />
<br />
# scp ~/.ssh/id_rsa.pub phone:.ssh/authorized_keys<br />
<br />
You should now be able to ssh directly into the phone without a password prompt.<br />
<br />
To disable password logins ('''after setting up key access''') edit /etc/init.d/dropbear and change the following line:<br />
<br />
DROPBEAR_EXTRA_ARGS=<br />
<br />
to <br />
<br />
DROPBEAR_EXTRA_ARGS="-s"<br />
<br />
You will need to restart dropbear for this to take effect.<br />
<br />
=== From FreeRunner to Desktop ===<br />
<br />
Generate the key:<br />
<br />
dropbearkey -t rsa -f id_rsa<br />
<br />
The output will look something like this:<br />
<br />
Will output 1024 bit rsa secret key to 'id_rsa'<br />
Generating key, this may take a while...<br />
Public key portion is:<br />
ssh-rsa AAAAB3Nza[...]<br />
Fingerprint: md5 ca:e8:f0:b7:f6:7b:c2:b6:b9:71:e4:45:86:a9:ff:b8<br />
<br />
Copy and paste the one line (in this example, starting with 'ssh-rsa' onto the end of the host's authorized_keys file (often in ~/.ssh/).<br />
<br />
From the phone, ssh with -i:<br />
<br />
ssh -i id_rsa user@host<br />
<br />
=== Changing host keys ===<br />
<br />
If you reflash, your hosts keys will change. Try this ~/.ssh/config snippet:<br />
<br />
Host moko<br />
HostName 192.168.0.202<br />
StrictHostKeyChecking no<br />
UserKnownHostsFile /dev/null<br />
User root<br />
<br />
This is suggested because ssh on your desktop may complain if the key matching a certain IP changes (stored in .ssh/known_hosts).<br />
<br />
== GUI on desktop through SSH ==<br />
<br />
To get the GUI on the FreeRunner onto the desktop via USB, you can use ssh as follows:<br />
<br />
ssh -l root -X -v 192.168.0.202<br />
<br />
Using this, run openmoko-finger-demo for example, and it will open up on the desktop. To get landscape view, just resize the GUI window on the desktop.<br />
<br />
If you get an error like this:<br />
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.Spawn.ExecFailed: dbus-launch failed to <br />
autolaunch D-Bus session: Autolaunch requested, but X11 support not compiled in.<br />
you need to set the DBUS_SESSION_BUS_ADDRESS environment variable to the value on the FreeRunner before launching the process from your desktop. You can find the value of this variable by using a command such as<br />
ps auxwwwwe | grep -m 1 DBUS_SESSION_BUS_ADDRESS<br />
Note that you must run that command on the FreeRunner. Back on your desktop, run the process you want with the ''env'' command like this:<br />
env DBUS_SESSION_BUS_ADDRESS=''dbus_address'' ''process''<br />
<br />
==Display Remote Applications on FreeRunner==<br />
<br />
To get desktop apps to show up on your FreeRunner, first log in:<br />
<br />
ssh -l root 192.168.0.202<br />
<br />
Then run:<br />
<br />
DISPLAY=:0 xhost +192.168.0.200<br />
<br />
After this you can close the ssh session. Back on the desktop computer, run:<br />
<br />
DISPLAY=openmoko:0 xclock<br />
<br />
Note that the xhost command will allow remote applications on 192.168.0.200 to access the X server. It will allow anyone on the desktop machine to access the X server of the neo, including snooping anything you type on it. To disallow remote applications again, run this in the neo:<br />
<br />
DISPLAY=:0 xhost -192.168.0.200<br />
<br />
<span id="bottom"></span> <br />
{{Languages|USB Networking}}<br />
<br />
[[Category:USB]]<br />
[[Category:Hardware]]<br />
[[Category:Implemented]]<br />
[[Category:Networking]]</div>DolfjeBot1http://openmoko.org/wiki/TimezoneTimezone2008-08-31T13:00:14Z<p>DolfjeBot1: Replacing 'Freerunner' with 'FreeRunner'</p>
<hr />
<div>== Timezone ==<br />
<br />
At this time, there is no preferences application to set the timezone of your Openmoko device.<br />
<br />
For now, either open the terminal application or log in to your Openmoko over the USB networking<br />
connection and change the timezone via commandline commands.<br />
<br />
To change the timezone on your FreeRunner you have to <br />
<br />
opkg install tzdata<br />
<br />
and then install one of these<br />
<br />
tzdata-africa<br />
tzdata-americas<br />
tzdata-antarctica<br />
tzdata-arctic<br />
tzdata-asia <br />
tzdata-atlantic<br />
tzdata-australia<br />
tzdata-europe<br />
tzdata-misc<br />
tzdata-pacific<br />
tzdata-posix <br />
tzdata-right<br />
<br />
after that, you should create a symlink named /etc/localtime which points to the appropriate file in /usr/share/zoneinfo. For example, if you're on the East Coast of the U.S., the following command will link the correct zoneinfo file to your /etc/localtime, giving you the correct time:<br />
<br />
ln -sf /usr/share/zoneinfo/America/New_York /etc/localtime<br />
<br />
for Germany for example it is TZ="Europe/Berlin"<br />
for France TZ="Europe/Paris"<br />
and so on<br />
<br />
Alternatively, you can take the more invasive approach and change the TZ="UTC" in your /etc/profile<br />
to the timezone you want.<br />
<br />
Once the timezone is set, restart of your x-server with <br />
<br />
/etc/init.d/xserver-nodm restart<br />
<br />
you should now have the right timezone.<br />
<br />
In the future, expect the time zone to be set automatically by the telephone stack once connected to the network.<br />
<br />
See also [[Date]] for setting the date and time.<br />
<br />
[[Category:Documentation]]<br />
[[Category:Guides]]<br />
[[Category:Preferences]]</div>DolfjeBot1http://openmoko.org/wiki/TangoGPSTangoGPS2008-08-31T12:59:46Z<p>DolfjeBot1: Replacing 'Freerunner' with 'FreeRunner'</p>
<hr />
<div>{{Languages|TangoGPS}}<br />
{{Application|TangoGPS}}<br />
<br />
__TOC__<br />
<br />
TangoGPS is a map application which can utilize Neo's built-in GPS to show your current location.<br />
<br />
[[Image:TangoGPS1.jpg]]<br />
<br />
Website: http://www.tangogps.org<br />
<br />
== Running tangoGPS on [[Om 2008.8]] ==<br />
<br />
{{note|There may be other steps because I remember it took a while before my TangoGPS started working, but these are the only things I remember installing}}<br />
<br />
From the freerunner connected to the internet:<br />
<br />
opkg install gpsd <br />
opkg install http://www.tangogps.org/downloads/tangogps_0.9.3-r1_armv4t.ipk<br />
<br />
If opkg complains about not being able to acquire a lock, try:<br />
<br />
pkill packagekit<br />
<br />
To get gpsd working on the FreeRunner you have to change the configuration according to [[Gpsd#GPS_on_GTA02]].<br />
Then start gpsd by:<br />
<br />
/etc/init.d/gpsd start<br />
<br />
If you get an error about no GPS device in /etc/default/gpsd execute:<br />
<br />
echo "GPS_DEV=\"/dev/ttySAC1\"" > /etc/default/gpsd<br />
<br />
Now you must power up the GPS-chip by opening the "Settings" application and setting the GPS entry to "on". Now you can run tangoGPS and wait until it get's a GPS fix. This can take up to a few minutes.<br />
<br />
== Running TangoGPS on [[debian]] ==<br />
<br />
Tangogps is a very nice GPS mapping application. The latest version is available in [[Debian]].<br />
<br />
Unfortunately it depends on gpsd which conflicts with frameworkd in fso-frameworkd.<br />
<br />
# apt-get install gpsd tangogps<br />
<br />
Edit <code>/etc/frameworkd.conf</code>. In the section <code>[ogpsd]</code>, edit to read:<br />
<pre><br />
# path = /dev/ttySAC1<br />
path = /dev/null<br />
</pre><br />
<br />
/etc/init.d/fso-frameworkd restart<br />
/etc/init.d/zhone-session stop && sleep 2 && /etc/init.d/zhone-session start <br />
<br />
# dpkg-reconfigure gpsd<br />
<br />
* Start gpsd automatically on boot? Yes.<br />
* Device the GPS receiver is attached to: /dev/ttySAC1<br />
* Should gpsd handle attached USB GPS receivers automatically? Yes<br />
** not certain what this answer should be<br />
* Options to gpsd: none<br />
<br />
<br />
Start tangogps like this:<br />
<br />
# echo 1 >/sys/devices/platform/s3c2440-i2c/i2c-adapter/i2c-0/0-0073/neo1973-pm-gps.0/pwron<br />
Turns the GPS on.<br />
<br />
# DISPLAY=:0 tangogps<br />
<br />
<br />
'''Issues:'''<br />
* The different daemons for reading GPS data mean that both tangogps and the framework demo GPS application can't be configured to work at the same time. Reboots are probably necessary when switching between them.<br />
** Both gpsd and the framework publish GPS data through dbus, though with different interfaces. This suggests a number of possible solutions.<br />
*** gpsd or the framework could implement the other's interface (along with their own).<br />
*** a translator could read one interface and emulate the other<br />
*** the framework could have an option to read data from gpsd.<br />
*** opgsd/gypsy could be extended to be backwards compatible with the majority of gps applications.<br />
<br />
== Downloading Maps for offline use ==<br />
tangoGPS can bunch-download the map images so you don't need an internet connection while walking around. By default tangoGPS stores downloaded maps to /tmp/. This folder is lost every time you reboo the device. But you can use the "Config" tab within tangoGPS to change the "Cache Dir" location to , for example, /osm/ . So downloaded maps will be kept in the Neos flash, also after reboot. This works fine on OM2007.2 and Debian. If this config gets lost during reboot file a bug against your distro.<br />
<br />
Once you have set the location to a non-volatile path, you can connect your Neo to the internet by USB or WiFi at home and start downloading the maps of your area. Tap the map screen and select "map download". Now on-the-road tangoGPS will be able to show you maps in different zoom levels even though you are not connected to the inet.<br />
<br />
== Downloading Maps via GPRS ==<br />
I think TangoGPS may have started working after I followed the instructions to get GPRS working with GSM multiplexing here: [[Manually_using_GPRS#Option_1:_With_GSM_multiplexing_and_with_a_GUI]]<br />
<br />
There are steps included in those instructions to improve GPS performance. The great thing is that once you get GPRS working, you can roam with TangoGPS running and have it download maps as needed over the GPRS connection!<br />
<br />
<br />
== Importing Tracks into TangoGPS ==<br />
<br />
TangoGPS is able to record and store a track in its native format, and [http://psung.blogspot.com/2008/07/sharing-gps-tracks-from-tangogps-on.html tools] exist to convert this to GPX.<br />
However, TangoGPS does not support the import of tracks. You may help yourself by using [http://relet.net/frog/archives/68 this tool] to import GPX trackpoints as a series of POIs directly into the sqlite database which tangoGPS uses to store POIs.<br />
<br />
== Using Google Maps with TangoGPS ==<br />
<br />
Go to Config and change the url to http://mt1.google.com/mt?&x=%d&y=%d&zoom=%d and check the "Inverted Zoom" box. Press save Repository Configuration and you're ready to go.<br />
:Automated map download will most certainly fail after a certain period of time, as Google is very keen on keeping leechers out.<br />
:It did work for me...<br />
<br />
[[Category:GPS Applications]]</div>DolfjeBot1http://openmoko.org/wiki/Switching_Keyboards_on_Om_2007.2Switching Keyboards on Om 2007.22008-08-31T12:59:34Z<p>DolfjeBot1: Replacing 'Freerunner' with 'FreeRunner'</p>
<hr />
<div>==Fix Default==<br />
<br />
Due to a bug, the default keyboard supplied on the 2007.2 doesn't allow you to enter the "/" or "\" characters, which should be on the same key (0?) as "+".<br />
You can instead add these characters to other keys, in this example ">" and "/" are added to the 1 key.<br />
You may also insert the tab character \t, which provides tab completion.<br />
The | character may also be useful.<br />
Edit <tt>/etc/multitap-pad/im-multipress.conf</tt>:<br />
<br />
[keys]<br />
KP_0 = +;=;/;\\<br />
KP_1 = .;,;/;>;-;?;!;@;:;(;)<br />
KP_2 = a;b;c;2<br />
KP_3 = d;e;f;3<br />
KP_4 = g;h;i;4<br />
KP_5 = j;k;l;5;\t<br />
KP_6 = m;n;o;6<br />
KP_7 = p;q;r;s;7<br />
KP_8 = t;u;v;8<br />
KP_9 = w;x;y;z;9<br />
KP_10 = A;B;C;2<br />
KP_11 = D;E;F;3<br />
KP_12 = G;H;I;4<br />
KP_13 = J;K;L;5<br />
KP_14 = M;N;O;6<br />
KP_15 = P;Q;R;S;7<br />
KP_16 = T;U;V;8<br />
KP_17 = W;X;Y;Z;9<br />
<br />
The buggy key is <tt>KP_0</tt> in the above file.<br />
<br />
The ; character is also missing. You can add this character by adding ;\; to any of the lines above.<br />
<br />
==Matchbox keyboard==<br />
<br />
Another keyboard is available: matchbox-keyboard. It is a full QWERTY keyboard. This howto is based on a blog entry which can be found [http://www.ginguppin.de/node/15 here]<br />
<br />
===What does the keyboard look like?===<br />
<br />
[[Image:Complete_QWERTY_Keyboard_On_The_FreeRunner_screenshot.png|none|thumb|260px|Screenshot of the keyboard applet]]<br />
<br />
===Considerations===<br />
<br />
Pros:<br />
* All keys can be generated<br />
* Takes up less space than the keypad (multitap-pad), leaving more space for the application<br />
<br />
Cons:<br />
* You pretty much have to use a stylus. With difficulty you can hit keys with the corner of a fingernail.<br />
<br />
<br />
===How to install it?===<br />
<br />
If you use a ScaredyCat release (http://buildhost.automated.it/OM2007.2/) or [http://downloads.openmoko.org/releases/Om2008.4/ Om2008.4], use the following:<br />
<br />
opkg remove -force-depends multitap-pad<br />
opkg install matchbox-keyboard-inputmethod<br />
opkg install matchbox-keyboard-im<br />
opkg install matchbox-keyboard-applet<br />
<br />
Otherwise, you'll have to download the ipk files from [http://www.ginguppin.de/files/keyboard-ipk.tar.bz2 here]. Assuming you have a working internet connection on your FreeRunner, you can do the following:<br />
<br />
cd /tmp<br />
mkdir matchbox-keyboard<br />
cd matchbox-keyboard<br />
wget http://www.ginguppin.de/files/keyboard-ipk.tar.bz2<br />
tar -jxf keyboard-ipk.tar.bz2<br />
opkg remove -force-depends multitap-pad<br />
opkg install matchbox-keyboard-inputmethod*.ipk<br />
opkg install matchbox-keyboard-im*.ipk<br />
opkg install matchbox-keyboard-applet*.ipk<br />
cd ..<br />
rm -rf matchbox-keyboard<br />
<br />
After that you'll have to restart the X server:<br />
/etc/init.d/xserver-nodm restart<br />
<br />
===How to add a keyboard toggle button===<br />
<br />
To add a button to enable showing / hiding the keyboard, edit <tt>/etc/matchbox/session</tt>. In the list of applets after <tt>--end-applets</tt>, add <tt>keyboard</tt>, and restart your X server<br />
<br />
===How to switch between matchbox-keyboard and multitap-pad===<br />
<br />
If you want to keep the multitap keyboard, but also be able to start up the matchbox-keyboard, you can follow these ugly instructions:<br />
<br />
First you must install matchbox-keyboard.<br />
opkg install matchbox-keyboard<br />
<br />
Do the following (from the terminal or an ssh session with DISPLAY=:0.0):<br />
killall multitap-pad<br />
matchbox-keyboard > /dev/null 2>&1 &<br />
<br />
(If you type the above commands with multitap, you have to leave off the redirection of matchbox-keyboard output, since several of the keys you need are missing.)<br />
<br />
Caveats: When you start the matchbox-keyboard, it stays up all the time. This will (among other things) prevent you from unlocking, since the keyboard covers the openmoko logo at the bottom of the lock screen. You will need to:<br />
# nohup multitap-pad -d &<br />
# killall matchbox-keyboard<br />
to close it down, and at least get the matchbox keyboard going again. You should do that any time you're going to leave the neo alone for any length of time, so you can unlock it later.<br />
<br />
To make sure you don't end up removing all your keyboard input capability, you can create a new .desktop file in /usr/share/applications/ for starting and closing the keyboard. This is pretty easy to do by copying and editing an existing .desktop file.<br />
<br />
<br />
==Modified Matchbox Keyboard: finger friendly==<br />
There is a modified Matchbox keyboard available on http://wiki.harnir.net/openmoko:keyboard-compressed .<br />
The keyboard can be controlled without stylus and also includes everything needed for terminal-use.<br />
<br />
==== Installation ====<br />
<br />
Download one of the files below, uncompress and put it in ''/usr/share/matchbox-keyboard/'' on your Neo FreeRunner:<br />
<br />
* [http://wiki.harnir.net/_media/openmoko:file:keyboard-compressed.xml.gz?id=openmoko%3Akeyboard-compressed&cache=cache general keyboard layout]<br />
* [http://wiki.harnir.net/_media/openmoko:file:keyboard-compressed-pl.xml.gz?id=openmoko%3Akeyboard-compressed&cache=cache Polish keyboard layout]<br />
<br />
If you want, you can change the name of the file to ''keyboard.xml'' or make a symlink to it. This way, ''matchbox-keyboard'' will use it automatically after next restart of the X server.<br />
<br />
Note: I've installed keyboard layout from [[http://atariland.net/~dreilly/openmoko/]] before making this one. Please inform me if my layout works without these modifications, or if they are needed.<br />
<br />
==== How does it look like? ====<br />
<br />
=== Default layout ===<br />
[[Image:Matchbox-keyboard-general.png]]<br />
* ^[ - Escape<br />
* ⇑ - Shift<br />
* ⌫ - Backspace<br />
* ⇔ - switch layout to the alternate<br />
* ^C - Control<br />
* ◆ - write a digit or symbol<br />
* ↵ - Enter<br />
<br />
<br />
=== Default Polish layout ===<br />
[[Image:Matchbox-keyboard-pl.png]]<br />
<br />
=== Shifted Polish layout ===<br />
<br />
[[Image:Matchbox-keyboard-pl-caps.png]]<br />
<br />
* ⇒ - Tab<br />
* ⇑⇑ - Caps Lock<br />
<br />
If you use general layout, special characters from the top row stay the same in the shifted layout.<br />
<br />
=== Digits and symbols ===<br />
<br />
[[Image:Matchbox-keyboard-symbols.png]]<br />
<br />
When you select a desired key in this layout, keyboard immediately returns back to the alphabet keys.<br />
<br />
=== Alternate kayboard layout ===<br />
<br />
[[Image:Matchbox-keyboard-alternate.png]]<br />
<br />
This layout is "persistent" - when you select a key it won't disappear by itself - you need to use the <key>⇔</key> key in the bottom-left corner of the keyboard to return to the default keyboard.<br />
<br />
Alternate layout is meant for easy writing of medium or long numbers (decimal or hex, hence the A-F letters), IP and MAC addresses, RGB values, etc. You can find here also direction keys (↑, ↓, ←, →) for easier movement operations.<br />
<br />
<br />
==Switch back to the original Openmoko keypad==<br />
<br />
If you for whatever reason need to switch back, here are the steps:<br />
opkg remove matchbox-keyboard-inputmethod matchbox-keyboard-im matchbox-keyboard-applet<br />
opkg install multitap-pad<br />
<br />
Comment or delete the following lines in /etc/gtk-2.0/gtk.immodules :<br />
#"/usr/lib/gtk-2.0/2.10.0/immodules/libmb-im-invoker.so"<br />
#"matchbox-im-invoker" "Virtual Keyboard" "" "" "*"<br />
<br />
Now restart the xserver:<br />
/etc/init.d/xserver-nodm restart<br />
<br />
[[Category:Openmoko]]<br />
[[Category:Technical]]<br />
[[Category:Om 2007.2]]</div>DolfjeBot1http://openmoko.org/wiki/SupportSupport2008-08-31T12:59:24Z<p>DolfjeBot1: Replacing 'Freerunner' with 'FreeRunner'</p>
<hr />
<div>== Frequently Asked Questions ==<br />
<br />
Please refer following link to FAQ<br />
<br />
[http://wiki.openmoko.org/wiki/Neo_FreeRunner_%28GTA02%29_FAQ#Frequently_Asked_Questions GTA02 FAQ]<br />
<br />
== General information needed during support==<br />
<br />
For user purchase from webshop, please provide following information in order to provide better suuport for you. Including:<br />
<br />
User Name<br />
e-mail<br />
Order number<br />
Contact information<br />
IMEI<br />
S/N<br />
P/N (could know it’s hardware version v5 or v6)<br />
Manufacture Date<br />
Date of purchase<br />
Location of purchase<br />
Issue description<br />
<br />
== Support Contact ==<br />
<br />
=== Technical Support ===<br />
<br />
Please subscribe support for Openmoko device owners list <support@lists.openmoko.org><br />
<br />
=== Repair/RMA/Return/Swap ===<br />
<br />
* Order from webshop, please conatct shop@openmoko.com<br />
<br />
* Get phone from distributor, please conatct distributor directly<br />
<br />
== Downloads ==<br />
<br />
=== FreeRunner (GTA02) ===<br />
<br />
* FreeRunner release images [http://buildhost.openmoko.org/releases/FreeRunner/ FreeRunner]<br />
<br />
=== ASU (August Software Update) (GTA02) ===<br />
<br />
* ASU development images: [http://downloads.openmoko.org/asu/ ASU]<br />
<br />
== Servers ==<br />
<br />
=== git ===<br />
<br />
* git.openmoko.org [http://git.openmoko.org/]<br />
<br />
Latest kernel, Qtopia, u-boot, k-boot, production testing software respository<br />
<br />
=== SVN ===<br />
<br />
* svn.openmoko.org [http://svn.openmoko.org/]<br />
<br />
Openmoko developer and drivers/utility development repsoitory, gta01 kernel development<br />
<br />
=== Buildhost ===<br />
<br />
* buildhost.openmoko.org [http://buildhost.openmoko.org/]<br />
<br />
Developer tools/sources and daily build images<br />
<br />
=== Download ===<br />
<br />
* downloads.openmoko.org [http://downloads.openmoko.org/]<br />
<br />
Official release stable tools/sources/images<br />
<br />
=== Bug/Development Trac ===<br />
<br />
* http://docs.openmoko.org/trac/<br />
<br />
Bug/Development track<br />
<br />
=== Application projects === <br />
<br />
* http://projects.openmoko.org/<br />
<br />
Application projects source forge<br />
<br />
[[Category:Basic End User]]</div>DolfjeBot1http://openmoko.org/wiki/Specialized_USB_cablesSpecialized USB cables2008-08-31T12:59:13Z<p>DolfjeBot1: Replacing 'Freerunner' with 'FreeRunner'</p>
<hr />
<div>{{note|work in progress}}<br />
<br />
== Attaching the Neo (acting as a USB host) to a USB device ==<br />
<br />
The USB port (5 position mini type B jack) on the Neo 1973 and Neo FreeRunner can be both a USB device or a USB host. The provided cable (5 position mini type B plug to type A plug) is used when attaching the Neo to a USB host.<br />
<br />
A specialized cable is required when attaching the Neo to a USB device, which provides a USB type A jack at the end.<br />
<br />
(picture)<br />
<br />
Alternately, an adapter capable of connecting two type A plugs will allow attaching the provided USB cable to the USB cable that came with the USB device. This adapter is also known as a gender changer. <br />
<br />
(picture)<br />
<br />
=== Ready-made mini type B plug to a type A jack cable ===<br />
<br />
You can buy [[http://www.jaykang.com/usbafetousbm1.html this]] ready-made USB A-Type Female to USB Mini-B Type 5 Pin Male Adapter.<br />
[[Image:jaykang_usbafetousbm1.jpg|thumb|none]]<br />
<br />
=== How to make a mini type B plug to a type A jack cable ===<br />
<br />
(picture, as soon as I build it)<br />
<br />
Parts list:<br />
<br />
* Mini type B plug: Digi-Key [[http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail?name=H2958-ND H2958-ND]]<br />
* type A jack: I have not yet been able to find a source for these. Meanwhile, use the jack from a standard USB extension cord<br />
* Cable: Ideally, the data lines should be twisted and 28 AWG, the power lines should be 20 or 28 AWG, e.g. Hitachi Cable [[http://www.hcm.hitachi.com/electronic_round_cable/bulk-usb-cable.shtml 49248 ]]<br />
<br />
Construction instructions:<br />
<br />
(TBA)<br />
<br />
=== Ready-made type A jack to a type A jack adapter (gender changer) ===<br />
<br />
You can buy [[http://www.jaykang.com/usbtyfetotyf.html this]] ready-made USB Type A Female to Female Gender Changer.<br />
[[Image:jaykang_usbtyfetotyf.jpg|thumb|none]]<br />
<br />
=== How to make a type A jack to a type A jack adapter (gender changer) ===<br />
<br />
This community provided instruction shows how to build an adapter from a USB socket salvaged from a computer motherboard.<br />
<br />
Note that these instructions are provided in the hope that they are useful but without any warranty!<br />
<br />
[[Image:2-usb-receptables.jpg|thumb|none]]<br />
<br />
:#Find an old motherboard with a set of two USB receptacles as shown above.<br />
:#Desolder this set of receptacles from the motherboard. This can be bit tricky but it is doable at least with a desoldering gun.<br />
:#Each receptacle has four pins. Use a multimeter to verify that you have no short circuits between the pins or the shield.<br />
:#Solder adjacent pins together (GND to GND, D- to D-, D+ to D+, VCC to VCC).<br />
:#(Optional) Build a test cable. Cut an USB cable with A plug into half, connect it a receptacle and again measure that you have no short circuits. Then connect the test cable to PC and verify that you see<br />
black GND<br />
green 0V<br />
white 0V<br />
red +5V<br />
:#FreeRunner is shipped with a mini-B-to-A-plug cable. Connect this to a receptacle.<br />
:#(Optional)Connect test cable to the other receptacle and verify that you see<br />
black GND<br />
green 0V<br />
white 0V<br />
red 0V<br />
when freerunner acts as a device and<br />
black GND<br />
green 0V<br />
white 0V<br />
red +5V<br />
when it acts as a host.<br />
:#At your own risk, switch freerunner to USB host mode and connect an USB device to the other receptacle of the adapter. Here's how the setup should look like:<br />
<br />
<gallery><br />
Image:Usb-gender-changer1.jpg<br />
Image:Usb-gender-changer2.jpg<br />
</gallery><br />
<br />
==== Compatibility ====<br />
<br />
The adapter works with kingston data traveller 4G memory stick and aiptec pencam webcam. However, for some reason (probably the missing 15k resistors at D+ and D-) it did not work with any of the tested USB keyboards or mice:<br />
usb 1-2: new full speed USB device using s3c2410-ohci and address 24<br />
usb 1-2: device descriptor read/64, error -62<br />
usb 1-2: device descriptor read/64, error -62<br />
usb 1-2: new full speed USB device using s3c2410-ohci and address 25<br />
usb 1-2: device descriptor read/64, error -62<br />
usb 1-2: device descriptor read/64, error -62<br />
usb 1-2: new full speed USB device using s3c2410-ohci and address 26<br />
usb 1-2: device not accepting address 26, error -62<br />
usb 1-2: new full speed USB device using s3c2410-ohci and address 27<br />
usb 1-2: device not accepting address 27, error -62<br />
<br />
However, if I connect neo to small (unpowered) USB hub<br />
usb 1-2: new full speed USB device using s3c2410-ohci and address 61<br />
usb 1-2: configuration #1 chosen from 1 choice<br />
hub 1-2:1.0: USB hub found<br />
hub 1-2:1.0: 4 ports detected<br />
and connect the keyboard to the hub then it is correctly recognized:<br />
usb 1-2.3: new low speed USB device using s3c2410-ohci and address 62<br />
usb 1-2.3: configuration #1 chosen from 1 choice<br />
input: USB Keyboard as /devices/platform/s3c2410-ohci/usb1/1-2/1-2.3/1-2.3:1.0/input/input13<br />
input: USB HID v1.10 Keyboard [ USB Keyboard] on usb-s3c24xx-2.3<br />
input: USB Keyboard as /devices/platform/s3c2410-ohci/usb1/1-2/1-2.3/1-2.3:1.1/input/input14<br />
input: USB HID v1.10 Device [ USB Keyboard] on usb-s3c24xx-2.3<br />
<br />
With the hub I can also use both keyboard and usb memory stick at the same time.<br />
<br />
==== Power consumption ====<br />
<br />
When I unplug the USB hub (with only keyboard connected to it) the power consumption estimate at /sys/devices/platform/bq2700-battery.0/power_supply/bat/current_now decreases from 175000 to 145000 (are these microamperes?).<br />
<br />
== How to make a USB cable for powering attached USB devices and charging the Neo while in host mode ==<br />
<br />
This cable might be necessary for a number of reasons, e.g. <br />
<br />
* The application requires that the Neo not become suspended<br />
* The application requires long run time<br />
* The attached USB device consumes a lot of power<br />
<br />
These instructions will show you how to make a cable with 3 ends:<br />
<br />
* A mini-USB type B cable for the Neo itself<br />
* A cable of whatever type to go to your USB device.<br />
* A cable going to a +5V +/-10%(max!) power supply with enough power for your device and to charge the Neo. This could be a wall charger or even another USB plug.<br />
<br />
You connect the Data+ and Data- wires of the Neo and the device, and connect all of the ground wires together and all of the +5V wires together. This powers the Neo and the device, while letting the neo talk to the device.<br />
You have to connect 2pcs 15kOhm resistors, one from D+ to ground, and one from D- to ground, to comply with USB-spec for hostmode, as Neo is switching off the internal resistors when you enable charging/powering over USB by asserting EN_USBHOST.<br />
See schematics, LOCATION:49XX<br />
<br />
Just for reference, the USB wires from left to right are:<br />
*Black: Power -<br />
*Green: Data -<br />
*White: Data +<br />
*Red: Power +<br />
<br />
The Mini_USB-B connector has a fifth pin, the ID-pin.<br />
This pin is supposed to be short to ground to signal FreeRunner to enter hostmode. For the Y-cable and enabling external power while in hostmode, you may connect a 47kOhm resistor from ID-pin to ground. This is the same trick the OM-wallcharger uses to signal to FreeRunner it can charge with 1A. Future kernels should switch to hostmode + external power when seeing this 47k resistor.<br />
<br />
<br />
<br />
<br />
[[Category:Neo1973 Hardware]]<br />
[[Category:Neo FreeRunner Hardware]]<br />
[[Category:USB]]</div>DolfjeBot1http://openmoko.org/wiki/Snapshot_review/2008-07-12Snapshot review/2008-07-122008-08-31T12:59:03Z<p>DolfjeBot1: Replacing 'Freerunner' with 'FreeRunner'</p>
<hr />
<div>===Snapshot History and Overview===<br />
Latest reviewed image: [[Snapshot_review/2008-07-12]]<br />
<br />
Latest Recommended image: [[Snapshot_review/2008-04-21]]<br />
<br />
Link to all [[:Category:SnapshotReview|previous snapshot reviews]].<br />
<br />
The latest kernel and root image recommended in these reviews will always be available [http://downloads.openmoko.org/recommended/ here]<br />
<br />
===Openmoko Snapshot Review Criteria===<br />
<br />
Date: 2008-07-12<br />
<br />
Rootfs Snapshot name:<br />
Openmoko-openmoko-devel-image-glibc-ipk-P1-Snapshot-20080712-om-gta02.rootfs.jffs2<br />
<br />
Kernel snapshot name:<br />
uImage-2.6.24+git20080424-om-gta02.bin<br />
<br />
uBoot Snapshot name:<br />
u-boot-gta02v5-1.3.1+svnr4297+gitb29661fc1151077776454288051bc9a488351ce8-r3.bin<br />
<br />
Device type:<br />
FreeRunner (GTA02v5)<br />
<br />
==Boot==<br />
*Speed - (No measured test.)<br />
*Error Messages - (No measured test.)<br />
*Failures - (No measured test.)<br />
<br />
==Phone Functionality==<br />
<br />
'''Incoming Calls'''<br />
<br />
# Can receive - Yes<br />
# Kinetic alert (vibrate) - Yes<br />
# Auditory alert (sound) - Yes<br />
# Call quality - Fine. The annoying echo heard by the caller has gone, even if was reproducible with the firmware from April 24 using the same phone. (Tested twice with both firmwares.) <br />
# Missed calls display on OM-today2 - Yes<br />
# Calls recorded in call log - Yes<br />
# Stability - The phone sometimes seems to abort calls after a few minutes. Calling again immediately afterwards works, though.<br />
<br />
'''Outgoing Calls'''<br />
# Can make - Yes<br />
# Call quality - Yes<br />
# Calls recorded in call log - Yes<br />
# Stability - The phone sometimes seems to abort calls after a few minutes. Calling again immediately afterwards works, though.<br />
<br />
==Messaging Functionality==<br />
'''Incoming SMS'''<br />
# Can receive - Yes<br />
# Kinetic alert (vibrate) - Yes<br />
# Auditory Altert (sound) - Yes<br />
# Sender identified if applicable - Yes<br />
# Is message readable - Yes<br />
# OM today2 displays new messages - Yes<br />
# Communication logged - Yes<br />
# Stability - Incoming SMS messages aren't matched against Contact list if entered using local format. [http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1345 Bug #1345 Reported]<br />
<br />
'''Outgoing SMS'''<br />
# Can send - Yes<br />
# Message readable - Yes<br />
# Delivery notification works - (No measured test.)<br />
# Communication logged - Yes<br />
# Stability - Good<br />
<br />
==Person Information Management==<br />
'''Contacts'''<br />
# Can add - Yes<br />
# Can create groups - Yes<br />
# Can modify - Yes<br />
<br />
'''Calendar'''<br />
# Can add events - Yes<br />
# Can view events - Yes<br />
# Can remove events - Yes<br />
# Events appear on openmoko-today2 - Yes<br />
# Events trigger kinetic alarm - Yes<br />
# Events trigger auditory alarm - Yes<br />
<br />
==Media Player==<br />
'''Music'''<br />
# Mp3 - Yes; Can even seek now.<br />
# Vorbis - Yes; Can even seek now.<br />
<br />
'''Video'''<br />
# Theora Playback - (No measured test.)<br />
# Theora Pause - (No measured test.)<br />
<br />
==GPS==<br />
- Can turn on - Yes<br />
- Can turn off - Yes<br />
<br />
==Bluetooth==<br />
# Can turn Bluetooth on - (No measured test.)<br />
# Can turn Bluetooth off - (No measured test.)<br />
<br />
==Battery Life==<br />
About 8 hours with heavy use (The 1st days with my phone...) - which was to be expected since the device was virtually never in suspend mode (see the Suspend section.)<br />
<br />
==Software Keyboard==<br />
# Keyboard type - Multi-tap<br />
# Displays correctly - Yes<br />
# Usability - Poor: Multi-tap input's lack of CTRL keys harms terminal use. But at least predictive. It is easy to install a better keyboard, though using opkg.<br />
<br />
==Suspend==<br />
# Suspend / Resume works: Many times fails to suspend; Sometimes won't resume again. <br />
# All features work after suspend / resume cycle: If the phone does come up again, Yes<br />
# Can receive incoming calls or sms while in suspend: Yes<br />
<br />
==User Feedback==<br />
Please provide feedback on how to improve these reviews. Also, please identify yourself when making changes.<br />
<br />
[[category:SnapshotReview]]</div>DolfjeBot1http://openmoko.org/wiki/Setting_Date_and_TimeSetting Date and Time2008-08-31T12:58:12Z<p>DolfjeBot1: Replacing 'Freerunner' with 'FreeRunner'</p>
<hr />
<div>Linux systems (such as the FreeRunner) prefer that the system clock be set to universal time (UTC). Then, you will need to configure the timezone to display the time adjusted to local time.<br />
<br />
See [[Timezone]] for instructions on changing the time zone.<br />
<br />
For more information on Linux timekeeping, see [http://www.linuxsa.org.au/tips/time.html Linux, Clocks, and Time]. (But ignore mentions of ''/etc/sysconfig/clock''. That doesn't apply to the Openmoko environment.)<br />
<br />
== Setting the date/time using "date" ==<br />
<br />
To change the date on your FreeRunner, issue one of the following commands:<br />
<br />
date -s ''MMDDhhmm''<br />
date -s ''MMDDhhmmYYYY''<br />
date -s ''MMDDhhmmYYYY.ss''<br />
<br />
where ''MM'' is the month, 01-12; ''DD'' is the day, 01-31; ''hhmm'' is the time, 0000-2359; ''YYYY'' is the optional year, and ''.ss'' is the optional seconds.<br />
<br />
== Setting date/time from your linux box ==<br />
<br />
ssh root@openmoko "date -u -s `date -u +%m%d%H%M%Y.%S`"<br />
<br />
== Setting the date/time automatically with NTP ==<br />
<br />
If your FreeRunner is connected to the internet, you can instead set the time automatically:<br />
<br />
opkg install ntpclient<br />
ntpclient -s -h pool.ntp.org<br />
<br />
If your FreeRunner is connecting to the internet through a USB host, make sure you allow UDP traffic to pass through on port 123 (NTP) on your host machine or you may get a "no route to host" error from ntpclient.<br />
<br />
== Syncing the hardware clock ==<br />
<br />
No matter which method you used above, sync the hardware clock with the system time to make your change persist over reboots:<br />
<br />
hwclock --systohc<br />
<br />
Note: if you run the [[ASU]] image, hwclock will not work. Instead you can use: <br />
<br />
echo "W\n" > /var/spool/at/trigger<br />
<br />
Here is a link from the community mailing list for using hwclock with the [[ASU]] image<br />
:http://lists.openmoko.org/pipermail/community/2008-July/023786.html<br />
<br />
== Setting the date/time automatically with gps ==<br />
<br />
[http://projects.openmoko.org/projects/gpv/ GPS Sight] has a button to sync the hardware clock to the gps clock.<br />
<br />
First you have to make sure gps works on you neo. You can do that by following the steps in the [[Getting_Started_with_your_Neo_FreeRunner#Use_the_GPS]].<br />
<br />
The second step is to install GPS Sight:<br />
<br />
# opkg install http://projects.openmoko.org/frs/download.php/227/gpssight_0.8.4_freerunner.armv4t.ipk<br />
<br />
The last step is the actual syncing of the clock. For this, simply run the GPS Sight program from the main menu, wait for it to find the gps time and click the button labeled "Sync clock".<br />
<br />
== Future Work ==<br />
<br />
Presumably it might also be possible to use gpspipe (or something else) to set the date once you have a gps fix automatically? In addition, the phone stack should set the date, time, and timezone once connected to a network.<br />
<br />
[[Category:Documentation|Date and Time]]<br />
[[Category:Guides|Date and Time]]<br />
[[Category:Preferences|Date and Time]]</div>DolfjeBot1http://openmoko.org/wiki/Server:WebProxyServer:WebProxy2008-08-31T12:58:02Z<p>DolfjeBot1: Replacing 'Freerunner' with 'FreeRunner'</p>
<hr />
<div>{{wishlist}}<br />
This is a brief page describing a web proxy optimised for use on devices with a reasonable amount of persistant storage, and very limited bandwidth.<br />
<br />
Once, each page linked to a subpage of contents, which remained static, and could be easily refreshed if it changed based on dates in the HTTP headers.<br />
<br />
Now, this is the case in the minority of popular sites.<br />
Most sites now have a substantial fraction of pages with some non-static contents.<br />
<br />
As an example of this, for example consider http://www.ebay.com/index.html.<br />
<br />
Over a 15 minute period, the size was constant at around 66K, and it was different most times it was loaded.<br />
<br />
Simply compressing this page using advanced compression techniques provides a useful compression - taking the page to 15K.<br />
<br />
A very simple test, using diff and gzip however, revealed that the variation between pages is quite small.<br />
<br />
This means that if the user clicks 'reload', if the proxy simply compresses the page, the user needs to download 15K.<br />
<br />
If, however, the user-agent and the proxy act in concert, this can be reduced to under 0.5K. (split on "<", count the compressed differences).<br />
<br />
This is done by the user-agent caching the pages it downloads, then informing the proxy of which version of the page it has.<br />
<br />
The proxy then simply sends the compressed differences between the previous and current version.<br />
<br />
=Q&A=<br />
* Would be better NOT to modify the client, but instead have a 'reassembly proxy' on the client, so that all http clients/user agents benefit without hacks. <br />
** This is a simple option initially.<br />
<br />
* How does this differ from rproxy? (http://ozlabs.org/~rusty/rproxy.html)<br />
** It differs primarily in that it does not require webservers to support anything. Only that a user desiring to run it has somewhere to put their personal proxy.<br />
** It also differs in that it has perfect knowledge of the state of the cache on the mobile device.<br />
** It differs significantly from rsync/rproxy, as the core of those programs - negotiating file differences over a remote link - is not done.<br />
** it does not require any negotiation over the (potentially very slow) link, and also enables the proxy to potentially send other changed pages that are referred in the changes.<br />
<br />
Other optimisations:<br />
* Comparing pages, and ensuring that any page has in fact changed before downloading, as many servers misreport pages changed when they have not.<br />
* Convert all jpegs to progressive, and initially only download the first 'scan' of the image, which is 1/8th the size or so. Allow the user to download the remainder of the file for full resolution by clicking on it.<br />
* Probably 'Ziproxy' (http://ziproxy.sourceforge.net/) could be extended to provide this functionality.<br />
<br />
Extended usage scenarios:<br />
* Different profiles, depending on how the FreeRunner is connected (Wifi vs. USB vs. GPRS).<br />
* Traffic-measurement especially for GPRS-connection for users with limited data-amounts (for example 200MB/month) or in areas with limited data-consumption, like on commercial wifi-aps on airports and such.<br />
<br />
[[Category:Server]]</div>DolfjeBot1http://openmoko.org/wiki/SFBayAreaGetStartedSFBayAreaGetStarted2008-08-31T12:57:24Z<p>DolfjeBot1: Replacing 'Freerunner' with 'FreeRunner'</p>
<hr />
<div>Hi ...<br />
<br />
If you are interested in attending a meeting to talk about Getting started with the FreeRunner in the San Francisco Bay Area (probably somewhere in the Peninsula/Milpitas/Fremont/San Jose areas) some time between July 15 and July 30, please indicate interest below:<br />
<br />
{|border=1<br />
!Name<br />
!Skills<br />
!Interest<br />
!Preferred Dates<br />
!Acceptable Locations (in order of preference)<br />
|-<br />
|[[User:Vvaidy|Vijay Vaidy]]<br />
|Programming<br />
|I want a fast, flexible Command-Line phone!<br />
|July 15-30<br />
|Peninsula, San Jose, Fremont, Milpitas, San Francisco<br />
|-<br />
|[[User:Elektrolott|Lothar]]<br />
|Programming<br />
|I don't have a FreeRunner yet (waiting for the 900MHz model)<br />
|I'll join if I can make it<br />
|San Jose<br />
|-<br />
|[[User:Brianwc|Brianwc]]<br />
|Documentation<br />
|Synchronized email, calendar, and contacts<br />
|Aug. 16-whenever<br />
|East Bay,Emeryville,Berkeley,Oakland<br />
|-<br />
|[[User:mcclen|Chris McClenaghan]]<br />
|Programming<br />
|Better, open personal communications<br />
|Anytime - July 14 looks good!<br />
|Monterey, SF Bay<br />
|-<br />
|[[User:yochaigal|Yochai Gal]]<br />
|Linux Admin/Technician<br />
|Application Testing/Phone Usage<br />
|Anytime<br />
|San Francisco, CA<br />
|-<br />
[[category:community]]<br />
[[category:Event]]</div>DolfjeBot1http://openmoko.org/wiki/Qtopia_on_FreeRunner/itQtopia on FreeRunner/it2008-08-31T12:56:56Z<p>DolfjeBot1: Replacing 'Freerunner' with 'FreeRunner'</p>
<hr />
<div>{{Languages|Qtopia_on_FreeRunner}}<br />
<br />
Questa pagina fornisce le istruzioni per installare Qtopia (la versione standard, non le varianti della [[ASU]] o della [[QtopiaOnX11]]) sul telefono GTA02 (FreeRunner). È simile alla pagina [[Qtopia on Neo1973]].<br />
<br />
{|align=right<br />
|__TOC__<br />
|}<br />
<br />
== Stato corrente ==<br />
L'8 Agosto 2008 Qtopia ha rilasciato [http://www.qtopia.net/modules/mydownloads/singlefile.php?lid=77 l'ultima immagine flash per il Neo FreeRunner della FIC (gta02)] contentente losnapshot di Qtopia 4.3.2 (Versione: 4.3.2-080808) dell'8 Agosto 2008 (versione GPL). <br />
<br />
Questa immagine può realmente fare e ricevere chiamate e messaggi di testo. Riesce a leggere tutti i contatti dalla scheda SIM (cosa che l'aggiornamento della 2007.2 sembra non sia in grado di fare). Contiene applicazioni che sembrano più stabili di quelle che si trovano sull'immagine della 2007.2. Fornisce diversi metodi per l'inserimento dei caratteri che sembrano più maturi. Non ha, comunque, un browser Web, né alcuna applicazione per il GPS.<br />
<br />
Puoi trovare tutte le immagini di Qtopia [http://www.qtopia.net/modules/mydownloads/viewcat.php?cid=6 qui].<br />
<br />
== Opzione 1: Flashare Qtopia sul FreeRunner ==<br />
Scarica l'immagine sopra indicata e segui queste istruzioni: [[Flashing the Neo FreeRunner]]<br />
<br />
== Opzione 2: Dual-Boot tra Qtopia e la 2007.2 (Qtopia caricato dalla scheda MicroSD) ==<br />
Requisiti d'istallazione: <br />
<br />
# Accesso tramite shell SSH all'immagine 2007.2 del FreeRunner tramite interfaccia USB o WLAN.<br />
# Una distribuzione anche desktop Linux (per scompattare l'immagine .jffs2, è funzionato anche usando una Ubuntu virtualizzata con VMWare)<br />
<br />
=== Preparare la scheda SD ===<br />
Controlla la [[Booting from SD#Prepare the SD card| Preparing the SD Card]] sezione della pagina [[Booting from SD]] per le istruzioni sul partizionamento e la formattazione. Dopo che avrai completato i passi per la "Formattazione della scheda SD", ritorna qui ed esegui i seguenti comandi:<br />
<br />
mount /dev/mmcblk0p1 /media/card<br />
mkdir /media/card/boot<br />
<br />
mkdir /media/mmcblk0p2<br />
mount /dev/mmcblk0p2 /media/mmcblk0p2<br />
<br />
Questi ti forniranno correttamente i requisiti per l'installazione del root filesystem e del kernel come di seguito indicato.<br />
<br />
=== Istallare Qtopia ===<br />
==== Estrarre l'immagine del root filesystem di Qtopia ====<br />
Scarica l'immagine FLASH di Qtopia da [[Latest Images#Qtopia image from qtopia.net]] sul tuo computer Linux ed estrai il suo contenuto:<br />
<br />
tar xzf qtopia-4.3.2-gta02-flash-*.tgz<br />
<br />
Dovresti trovarti con due files: <br />
#uImage-2.6.24+git18+9c058ff0d2641df3c36fc3300acb72078d2c41d4-r0-om-gta02.bin<br />
#qtopia-4.3.2-gta02-rootfs-07172049.jffs2 <br />
Ora estrai il root filesystem dal file jffs2 usando il comando che trovi [[Userspace root image#Mounting the JFFS2 image on a loop back device (Block Memory MTD Emulation) |qui]].<br />
<br />
==== Creare un tarball compresso ====<br />
Ora archivia e comprimi il root filesystem:<br />
<br />
# tar czf qtopia-4.3.2-gta02-rootfs-07172049.tar.gz <mountpoint> .<br />
<br />
Dove ''<mountpoint>'' è la directory dove il filesystem jffs2 è stato montato.<br />
<br />
==== Installare il Filesystem Root ====<br />
Trasferisci il tarball compressed sulla seconda partizione della MicroSD che è montata sul FreeRunner:<br />
<br />
scp qtopia-4.3.2-gta02-rootfs-07172049.tar.gz root@192.168.0.202:/media/mmcblk0p2/<br />
<br />
Loggati sul tuo FreeRunner e spacchetta il filesystem root:<br />
<br />
cd /media/mmcblk0p2<br />
tar xzf qtopia-4.3.2-gta02-rootfs-07172049.tar.gz<br />
rm qtopia-4.3.2-gta02-rootfs-07172049.tar.gz<br />
rm -f /media/mmcblk0p2/boot/*<br />
<br />
'''''Nota:''''' l'ultimo passaggio rimuove l'immagine del kernel dalla seconda partizione. Infatti U-Boot non può trovare il file uImage.bin nella prima partizione se un'immagine del kernel esiste nella directory boot/ sulla seconda partizione.<br />
<br />
==== Installare il Kernel ====<br />
Dalla tua Linux box rinomina il file <tt>uImage-2.6.24+git18+9c058ff0d2641df3c36fc3300acb72078d2c41d4-r0-om-gta02.bin</tt> come <tt>uImage.bin</tt> e copialo nella directory di boot sulla prima partizione della MicroSD. Dipendendo dalla versione di U-Boot che hai installato, questo potrebbe non funzionare. Per supportare ogni possibile versione, mettine una copia anche nella directory <tt>/media/card</tt>. C'è abbastanza spazio nella prima partizione da permetterci di acere <tt>uImage.bin</tt> in entrambi i posti.<br />
<br />
mv uImage-2.6.24+git18+9c058ff0d2641df3c36fc3300acb72078d2c41d4-r0-om-gta02.bin uImage.bin<br />
scp uImage.bin root@192.168.0.202:/media/card/boot/<br />
scp uImage.bin root@192.168.0.202:/media/card/<br />
<br />
== Option 3: updating from source ==<br />
<br />
{{note|This will upgrade only opt/Qtopia directory, you should use opkg update/upgrade for the rest}}<br />
Original Qtopia images (the distribution released by Trolltech, not ASU) are rarely released as a rootfs image, but the source code is often updated. If you want to reflash your OM with the latest version of Qtopia you might build it from sources. This has been explained in [http://lists.openmoko.org/pipermail/community/2008-August/024785.html this thread] of the community mailing list. Summing up:<br />
<br />
* get the latest toolchain released by trolltech: http://www.qtopia.net/modules/mydownloads/singlefile.php?lid=38 and unzip it on your PC (as root)<br />
cd /<br />
wget http://qtopia.net/downloads/neo/arm920t-eabi-ficgta01-toolchain.tgz<br />
tar xvzf arm920t-eabi-ficgta01-toolchain.tgz<br />
* get the latest snapshot from trolltech: ftp://ftp.trolltech.com/qtopia/snapshots/<br />
* once dowloaded untar it<br />
tar xvzf qtopia-opensource-src-4.3.2-snapshot-20080806.tar.gz<br />
* make a "build" dir <br />
mkdir build<br />
cd build<br />
* configure and make:<br />
../qtopia-opensource-src-4.3.2-snapshot-20080806/configure -device ficgta01<br />
make <br />
This will take some time (couple hours). Note that the option "-device ficgta01" should work for both neo and freerunner. Then:<br />
<br />
make install<br />
<br />
will make a root directory into build directory. That directory should be copied to /opt/Qtopia of your phone with scp. once done restart qpe or whole phone.<br />
<br />
== Lanciare Qtopia ==<br />
Ora spegni il FreeRunner<br />
<br />
shutdown -h now<br />
<br />
Log into U-Boot in the NOR Flash to boot from the MicroSD card: (instructions from [[Booting the Neo FreeRunner]])<br />
<br />
* Press and hold Power button<br />
* Then while still pressing the Power button, press and hold AUX button for 5 to 8 seconds. <br />
* A boot menu will appear. <br />
* Press the AUX button to select "[[Boot from sd card|Boot from MicroSD]]" and then press the Power button to execute.<br />
<br />
Qtopia should now boot.<br />
<br />
'''''Note:''''' you may get a kernel panic which says that "optional features not supported". If this is the case, boot back into 2007.2 and run<br />
<br />
umount /dev/mmcblk0p2<br />
fsck.ext3.e2fsprogs /dev/mmcblk0p2<br />
<br />
This will clean up the file system and clear recovery flags in ext3 that ext2 does not support, then try booting from the MicroSD again.<br />
<br />
== Internationalization ==<br />
<br />
Qtopia comes with support for German and American English, and users from other countries will find that Qtopia's predictive keyboard makes writing in another language near impossible. One way to disable the predictive keyboard is to simply replace /opt/Qtopia/etc/dict/en_US/common.dawg and words.dawg with empty files (after backing them up). Qtopia normally looks in these files for words to suggest, and if it doesn't find any words that fit, it simply shows what you actually wrote.<br />
<br />
Adding characters to the keyboard requires modifications to the source code, as described [http://www.qtopia.net/modules/newbb_plus/viewtopic.php?topic_id=512&forum=16 here].<br />
<br />
[[Category:Distributions/it]]<br />
[[Category:Qtopia/it]]</div>DolfjeBot1http://openmoko.org/wiki/Qtopia_/_Qt_Extended_on_FreeRunnerQtopia / Qt Extended on FreeRunner2008-08-31T12:56:46Z<p>DolfjeBot1: Replacing 'Freerunner' with 'FreeRunner'</p>
<hr />
<div>{{Languages|Qtopia_on_FreeRunner}}<br />
<br />
This page provides instructions on how to install Qtopia (proper, not the [[ASU]] or [[QtopiaOnX11]] efforts) on the GTA02 (FreeRunner) phone. It is similar to the [[Qtopia on Neo1973]] page.<br />
<br />
{|align=right<br />
|__TOC__<br />
|}<br />
<br />
== Current status ==<br />
On 08 August 2008, Qtopia released the [http://www.qtopia.net/modules/mydownloads/singlefile.php?lid=77 latest flash image for the FIC Neo FreeRunner (gta02)] containing the Qtopia 4.3.2 snapshot (Version: 4.3.2-080808) of 08 August 2008 (GPL version). <br />
<br />
This image can successfully make and receive calls and text messages. It can read all contacts from the SIM card (which the updated 2007.2 does not appear to be able to do). It contains apps that appear to be more stable than the ones found in the 2007.2 image. It has multiple input methods that appear to be more mature. It does not, however, have a web browser or a GPS application.<br />
<br />
You can find all the Qtopia images [http://www.qtopia.net/modules/mydownloads/viewcat.php?cid=6 here]<br />
<br />
== Option 1: Flashing Qtopia to FreeRunner ==<br />
<br />
Download the image mentioned above and follow the instructions here: [[Flashing the Neo FreeRunner]]<br />
<br />
== Option 2: Dual-Booting between Qtopia and 2007.2 (Qtopia boots from MicroSD card) ==<br />
<br />
Installation Requirements: <br />
<br />
# SSH shell access to 2007.2 based image of the FreeRunner through USB interface or WLAN.<br />
# A Desktop Linux distro (to unpack the .jffs2 image, I ran Ubuntu under VMWare)<br />
<br />
<br />
=== Preparing the SD card ===<br />
<br />
See the [[Booting from SD#Prepare the SD card| Preparing the SD Card]] section of the [[Booting from SD]] page for partitioning and formatting instructions. After you complete the "Formatting the SD Card" steps, return here and execute the following:<br />
<br />
mount /dev/mmcblk0p1 /media/card<br />
mkdir /media/card/boot<br />
<br />
mkdir /media/mmcblk0p2<br />
mount /dev/mmcblk0p2 /media/mmcblk0p2<br />
<br />
This will set you up properly for the installation of the root filesystem and the kernel in the steps below.<br />
<br />
=== Installing Qtopia ===<br />
<br />
==== Unpacking the Qtopia Root Filesystem Image ====<br />
<br />
Download the Qtopia FLASH image from [[Latest Images#Qtopia image from qtopia.net]] to your Linux box and extract its contents:<br />
<br />
tar xzf qtopia-4.3.2-gta02-flash-*.tgz<br />
<br />
You should now have two files: <br />
#uImage-2.6.24+git18+9c058ff0d2641df3c36fc3300acb72078d2c41d4-r0-om-gta02.bin<br />
#qtopia-4.3.2-gta02-rootfs-07172049.jffs2 <br />
Now, mount the root file system from the jffs2 using the commands found [[Userspace root image#Mounting the JFFS2 image on a loop back device (Block Memory MTD Emulation) |here]].<br />
<br />
==== Creating a compressed tarball ====<br />
<br />
Next, tar up the root filesystem:<br />
<br />
# tar czf qtopia-4.3.2-gta02-rootfs-07172049.tar.gz -C <mountpoint> .<br />
<br />
Where ''<mountpoint>'' is the location where the jff2 filesystem was mounted.<br />
<br />
==== Installing Root Filesystem ====<br />
<br />
Transfer this compressed tarball to the second partition of the MicroSD that is mounted on the FreeRunner:<br />
<br />
scp qtopia-4.3.2-gta02-rootfs-07172049.tar.gz root@192.168.0.202:/media/mmcblk0p2/<br />
<br />
Log in to your FreeRunner and unpack the root filesystem:<br />
<br />
cd /media/mmcblk0p2<br />
tar xzf qtopia-4.3.2-gta02-rootfs-07172049.tar.gz<br />
rm qtopia-4.3.2-gta02-rootfs-07172049.tar.gz<br />
rm -f /media/mmcblk0p2/boot/*<br />
<br />
'''''Note:''''' the last step removes the kernel image from the second partition. For some reason, U-Boot cannot find the uImage.bin file in the first partition if a kernel image exists in the second partition boot/ directory.<br />
<br />
==== Installing Kernel ====<br />
<br />
From your Linux box, rename <tt>uImage-2.6.24+git18+9c058ff0d2641df3c36fc3300acb72078d2c41d4-r0-om-gta02.bin</tt> to <tt>uImage.bin</tt> and copy it to the boot directory on the first partition of the MicroSD card. Depending on the version of U-Boot you have installed, this may not work. To prevent any possible issues, copy it to the <tt>/media/card</tt> directory as well. There is plenty of room on the first partition to have <tt>uImage.bin</tt> in both locations.<br />
<br />
mv uImage-2.6.24+git18+9c058ff0d2641df3c36fc3300acb72078d2c41d4-r0-om-gta02.bin uImage.bin<br />
scp uImage.bin root@192.168.0.202:/media/card/boot/<br />
scp uImage.bin root@192.168.0.202:/media/card/<br />
<br />
== Option 3: updating from source ==<br />
<br />
{{note|This will upgrade only opt/Qtopia directory, you should use opkg update/upgrade for the rest}}<br />
Original Qtopia images (the distribution released by Trolltech, not ASU) are rarely released as a rootfs image, but the source code is often updated. If you want to reflash your OM with the latest version of Qtopia you might build it from sources. This has been explained in [http://lists.openmoko.org/pipermail/community/2008-August/024785.html this thread] of the community mailing list. Summing up:<br />
<br />
* get the latest toolchain released by trolltech: http://www.qtopia.net/modules/mydownloads/singlefile.php?lid=38 and unzip it on your PC (as root)<br />
cd /<br />
wget http://qtopia.net/downloads/neo/arm920t-eabi-ficgta01-toolchain.tgz<br />
tar xvzf arm920t-eabi-ficgta01-toolchain.tgz<br />
* get the latest snapshot from trolltech: ftp://ftp.trolltech.com/qtopia/snapshots/<br />
* once dowloaded untar it<br />
tar xvzf qtopia-opensource-src-4.3.2-snapshot-20080806.tar.gz<br />
* make a "build" dir <br />
mkdir build<br />
cd build<br />
* configure and make:<br />
../qtopia-opensource-src-4.3.2-snapshot-20080806/configure -device ficgta01<br />
make <br />
This will take some time (couple hours). Note that the option "-device ficgta01" should work for both neo and freerunner. Then:<br />
<br />
make install<br />
<br />
will make a root directory into build directory. That directory should be copied to /opt/Qtopia of your phone with scp. once done restart qpe or whole phone.<br />
<br />
== Booting into Qtopia ==<br />
<br />
Now shutdown the FreeRunner<br />
<br />
shutdown -h now<br />
<br />
Log into U-Boot in the NAND Flash to boot from the MicroSD card: (instructions from [[Booting the Neo FreeRunner]])<br />
<br />
* Press and hold Power button<br />
* Then while still pressing the Power button, press and hold AUX button for 5 to 8 seconds. <br />
* A boot menu will appear. <br />
* Press the AUX button to select "[[Boot from sd card|Boot from MicroSD]]" and then press the Power button to execute.<br />
<br />
Qtopia should now boot.<br />
<br />
'''''Note:''''' you may get a kernel panic which says that "optional features not supported". If this is the case, boot back into 2007.2 and run<br />
<br />
umount /dev/mmcblk0p2<br />
fsck.ext3.e2fsprogs /dev/mmcblk0p2<br />
<br />
This will clean up the file system and clear recovery flags in ext3 that ext2 does not support, then try booting from the MicroSD again.<br />
<br />
== Internationalization ==<br />
<br />
Qtopia comes with support for German and American English, and users from other countries will find that Qtopia's predictive keyboard makes writing in another language near impossible. One way to disable the predictive keyboard is to simply replace /opt/Qtopia/etc/dict/en_US/common.dawg and words.dawg with empty files (after backing them up). Qtopia normally looks in these files for words to suggest, and if it doesn't find any words that fit, it simply shows what you actually wrote.<br />
<br />
Adding characters to the keyboard requires modifications to the source code, as described [http://www.qtopia.net/modules/newbb_plus/viewtopic.php?topic_id=512&forum=16 here].<br />
<br />
[[Category:Qtopia]]</div>DolfjeBot1http://openmoko.org/wiki/Press_CoveragePress Coverage2008-08-31T12:56:14Z<p>DolfjeBot1: Replacing 'Freerunner' with 'FreeRunner'</p>
<hr />
<div>{|align=right<br />
|__TOC__<br />
|}<br />
[http://www.google.com/trends?q=openmoko%2Cneo1973&ctab=1&geo=all&date=all Openmoko and Neo1973 on google trends.]<br />
<br />
This site contains the press coverage about Openmoko and the Neo 1973 sorted by language and date. Newest on top. See also [[FreeRunner:_Selected_Blogs_and_Articles]] for reviews by bloggers.<br />
<br />
== Languages ==<br />
<br />
=== English ===<br />
<br />
*Current search for news:<br />
**http://news.google.com/news?q=openmoko+phone<br />
**http://news.google.com/news?q=free-runner+phone<br />
<br />
==== August 2008 ====<br />
<br />
* Slashdot [http://mobile.slashdot.org/article.pl?sid=08/08/24/1739200 Canadian Firms Get Behind OpenMoko/FreeRunner]<br />
* BetaNews [http://www.betanews.com/article/Openmoko_to_publish_open_phone_recipes_after_dealing_with_NDAs/1218225833 Openmoko to publish 'open' phone recipes, after dealing with NDAs]<br />
* The Register [http://www.theregister.co.uk/2008/08/07/openmoko_opens_schematics/ Openmoko to reveal Linux phone's inner workings]<br />
* BusinessWire [http://www.smartbrief.com/news/cea/industryBW-detail.jsp?id=892DE460-3982-4B33-80D1-04B1D075BC1C Openmoko Declares Another Freedom: Publishes Schematics for Neo Phones]<br />
* Manufacturing Businesss Technology [http://www.mbtmag.com/articleXml/LN833223678.html Openmoko Declares Another Freedom: Publishes Schematics for Neo Phones; Openmoko Shows Beauty Is More Than Skin Deep]<br />
* LinuxDevices.com [http://www.linuxdevices.com/news/NS9423733896.html Open phone hardware vendor frees schematics]<br />
* New York Times [http://www.nytimes.com/2008/08/04/technology/04open.html?_r=1&ref=technology&oref=slogin Applications Spur Carriers to Relax Grip on Cellphones]<br />
<br />
==== July 2008 ====<br />
* MarketWatch [http://www.marketwatch.com/news/story/linuxworld-conference--expo-2008/story.aspx?guid={FBD51DEB-5D03-49F9-908E-7EA75596FC6A}&dist=hppr LinuxWorld Conference & Expo 2008 Kicks off Next Week in San Francisco]<br />
<br />
* Wired: [http://blog.wired.com/gadgets/2008/07/first-openmoko.html?cid=124704314 First Openmoko Custom Phone Now Available and Wears a Debian Plaid Kilt]<br />
<br />
* CNET: [http://news.cnet.com/8301-13505_3-9994040-16.html Free Software Foundation hates the iPhone, proposes ugly alternative]<br />
<br />
* PC World (Australia): [http://www.pcworld.idg.com.au/index.php?id=1584423557 FreeRunner Linux phone sells out, more on the way]<br />
<br />
* Slashdot: [http://tech.slashdot.org/article.pl?sid=08/07/15/1650208 First North American Openmoko/FreeRunners Arrive]<br />
<br />
* LinuxInsider: [http://www.linuxinsider.com/story/Linux-Edges-One-Step-Closer-to-Total-World-Domination-63798.html Linux Edges One Step Closer to Total World Domination]<br />
<br />
* LinuxDevices.com: [http://www.linuxdevices.com/news/NS5292286134.html First look at Openmoko software]<br />
<br />
* The InformationWeek: [http://www.informationweek.com/blog/main/archives/2008/07/when_is_a_phone.html When is a phone not a phone]<br />
<br />
* The New York Times: [http://www.nytimes.com/2008/07/10/technology/personaltech/10phone.html An Open-Source Cellphone (Tinkerers, Have a Ball)] <br />
<br />
* Ars Technica: [http://arstechnica.com/reviews/os/open-moko-software.ars First Look: Openmoko's Linux-based open smartphone platform]<br />
<br />
* Gearlog: [http://www.gearlog.com/2008/07/openmoko_releases_open_source.php Openmoko Releases Open Source Neo FreeRunner Phone]<br />
<br />
* PC Magazine: [http://www.pcmag.com/article2/0,2817,2324502,00.asp Report: Openmoko Open-Source Phone Goes Live July 4]<br />
<br />
* Information Week: [http://www.informationweek.com/blog/main/archives/2008/07/openmoko_in_the.html Openmoko In The U.S. -- And Maybe In My Hands, Too]<br />
<br />
* The Channel Wire: [http://www.crn.com/retail/208802464 Openmoko Celebrates July 4 With Linux-Based Smart Phone]<br />
<br />
* tmcnet.com: [http://internetcommunications.tmcnet.com/topics/broadband-mobile/articles/33168-openmoko-declares-independence-the-mobile-phone-neo-freerunner.htm Openmoko Declares Independence for the Mobile Phone: Neo FreeRunner Hits Market]<br />
<br />
* The Tech Herald: [http://www.thetechherald.com/article.php/200828/1420/Openmoko-s-Neo-FreeRunner-delivers-open-source-mobile-communication Openmoko’s Neo FreeRunner delivers open-source mobile communication]<br />
<br />
* ABC Channel 7: [http://abclocal.go.com/kgo/story?section=news/drive_to_discover&id=6248649 New phones offer ultimate customization] Please click on 2 of 2, then play the video.<br />
<br />
* FT.com: [http://blogs.ft.com/techblog/2008/07/freerunner-no-longer-has-a-free-run-at-open-source/ FreeRunner no longer has a free run at open source]<br />
<br />
* Location News: [http://location.net.in/news/viewn.asp?id=GIS:N_ncwodpuvkj Openmoko’s New Smartphone: the Neo FreeRunner]<br />
<br />
* WIRED Blog Network: [http://blog.wired.com/gadgets/2008/07/post-1.html Openmoko Neo FreeRunner on Sale July 4]<br />
<br />
* geek.com: [http://www.geek.com/openmoko-to-launch-neo-freerunner-july-4th-20080703/ Openmoko to launch Neo FreeRunner July 4th]<br />
<br />
* linuxdevices: [http://www.linuxdevices.com/news/NS9034757879.html It's a Yankee Doodle Linux Phone]<br />
<br />
* BusinessWire: [http://www.businesswire.com/portal/site/google/?ndmViewId=news_view&newsId=20080702005242&newsLang=en Openmoko Declares Independence for the Mobile Phone: Neo FreeRunner to Hit the Market July 4]<br />
<br />
==== June 2008 ====<br />
<br />
* Ars Technica: [http://arstechnica.com/news.ars/post/20080703-openmoko-freerunner-to-launch-on-july-4.html Openmoko FreeRunner Linux phone to launch on July 4]<br />
<br />
* The Register: [http://www.reghardware.co.uk/2008/07/03/openmoko_os_hanset/ Openmoko to release Linux handset tomorrow]<br />
<br />
* Kernel Trap: [http://kerneltrap.org/mailarchive/openmoko-community/2008/6/27/2256424 openmoko-announce: Let us impact the material world]<br />
<br />
* LinuxDevices.com: [http://www.linuxdevices.com/news/NS9978560959.html Open source phone goes mass-market]<br />
<br />
* BusinessWire: [http://www.businesswire.com/portal/site/google/?ndmViewId=news_view&newsId=20080625005431&newsLang=en Openmoko Signs Five Distributors for FreeRunner Open Source Mobile Phone]<br />
<br />
* Mobile Gazette: [http://www.mobilegazette.com/openmoko-neo-freerunner-08x06x26.htm Openmoko Neo FreeRunner]<br />
<br />
* ars technica: [http://arstechnica.com/news.ars/post/20080626-linux-phones-get-boost-with-openmoko-distribution-agreement.html Linux phones get boost with Openmoko distribution agreement]<br />
<br />
* SEECS Open Mobile Group: [http://seecsopenmobile.wordpress.com/2008/06/17/ The True Open Phone Platform]<br />
<br />
==== May 2008 ====<br />
<br />
*arstechnica.com, May 22, 2008, [http://arstechnica.com/news.ars/post/20080522-openmoko-linux-mobile-phone-ditches-gtk-gets-qt-and-e17.html Openmoko Linux mobile phone ditches GTK+, gets Qt and E17].<br />
<br />
*wordpress.com, May 19, 2008 , [http://gettingstartedopenmoko.wordpress.com/2008/05/19/openmoko-software-update/ Openmoko “April Software Update” (ASU) and Qtopia].<br />
<br />
<br />
==== March 2008 ====<br />
<br />
* Jack Kapica's Cyberia: [http://www.theglobeandmail.com/servlet/story/RTGAM.20080304.WBcyberia20080304133308/WBStory/WBcyberia Linux Goes Walkabout] (in ''Globe and Mail'' Online)- overview, also covers the CAD file release and notes that FreeRunner will put downward pressure on fees the Carriers charge consumers.<br />
<br />
==== February 2008 ====<br />
<br />
* Ars Technica at SCALE: [http://arstechnica.com/news.ars/post/20080211-the-enlightened-future-of-openmoko-linux-mobile-phones.html Interview with Carsten Haitzler]<br />
<br />
* SCALE Conference: [http://www.socallinuxexpo.org/blog/2008/02/03/interview-with-michael-shiloh-of-openmoko/ Interview with Michael Shiloh]<br />
<br />
==== January 2008 ====<br />
<br />
* Linux Devices: [http://linuxdevices.com/news/NS2393777675.html User-modifiable Linux phone upgraded]<br />
* ACIA 19th Jan 2008: [http://meeting.creativecommons.org.tw/program:the-making-of-a-totally-open-phone The making of an open phone]<br />
*reuters.com, Jan 14, 2008, [http://www.reuters.com/article/pressRelease/idUS97607+14-Jan-2008+BW20080114 Openmoko Signs Deal With German Distributor Pulster].<br />
<br />
==== December 2007 ====<br />
<br />
* The Information Week: [http://www.informationweek.com/blog/main/archives/2008/01/can_openmokos_o.html Can Openmoko's Open Source Handset Compete With Android?]<br />
<br />
* DigiTimes: Freeing your phone: Q&A with Sean Moss-Pultz, president of Openmoko [http://209.85.135.104/search?q=cache:Wu4YfufkOYMJ:www.digitimes.com/news/a20071204VL200.html+http://www.digitimes.com/news/a20071204VL200.html&hl=de&ct=clnk&cd=1&gl=de&client=opera Part I (cache)] [http://www.digitimes.com/telecom/a20071204VL202.html Part II]<br />
<br />
* The Linux Link Tech Show: Interview with Michael Shiloh, Openmoko Developer Relations Manager. Audio Files:[http://www.tllts.org/audio/tllts_221-11-28-07.ogg][http://www.tllts.org/audio/tllts_221-11-28-07.mp3]<br />
<br />
==== October 2007 ====<br />
* [http://www.news.com/Trolltech-axes-the-Greenphone/2100-1037_3-6214641.html Trolltech axes the Greenphone and recommends the Neo1973 device]<br />
* Wired preview called [http://www.wired.com/gadgets/wireless/news/2007/10/openmoko_firstlook?currentPage=all A First Tussle With Linux's iPhone Killer: The Openmoko Neo1973]<br />
* [http://radar.oreilly.com/archives/2007/10/dash_web2summit_openmoko.html Dash and Openmoko] Tim O'Reilly comments on [http://dash.net/ Dash, the connected GPS] and notes that it is based on the Openmoko software stack and derived from the Neo1973 hardware.<br />
* [http://www.wired.com/gadgets/gadgetreviews/magazine/test2007/st_essay Why Wireless Carriers Cripple Your Cell Phone] on [http://www.wired.com Wired Test] reports what we already know, that wireless carriers put more priority into protecting their "antediluvian business" model than into innovation. Of the Openmoko project it carries few details, but says "That's pretty cool"<br />
* [http://www.linuxjournal.com/article/9768#mpart4 Ten Questions for Sean Moss-Pultz], Program Manager of Openmoko<br />
<br />
==== September 2007 ====<br />
* [http://abclocal.go.com/kgo/story?section=drive_to_discover&id=5671823 ABC News] Building A Cell Phone From Scratch ([http://yamato.hyte.de/moko/openmoko_gumstix_neo_abcnews_h264_mp3.avi avi])<br />
* [http://www.phoronix.com/scan.php?page=news_item&px=NjA0NQ phoronix.com] Openmoko Schedule Revised, For X-Mas<br />
* [http://www.tectonic.co.za/view.php?src=rss&id=1739 tectonic.co.za] Linux picks up pace on cellphones<br />
<br />
==== August 2007 ====<br />
* [http://lwn.net/Articles/247187/ LWN] A first look at the Openmoko Neo 1973<br />
* [http://www.roughlydrafted.com/RD/RDM.Tech.Q3.07/B10AE668-EAD3-46DC-A042-5EF3461D63EF.html roughlydrafted.com] Apple iPhone vs the FIC Neo1973 Openmoko Linux Smartphone<br />
* [http://www.macworld.com/news/2007/08/02/openmoko/index.php Macworld] Portrait of a Linux iPhone-killer wannabe<br />
* [http://www.phoronix.com/?page=news_item&px=NTk1Mw Phoronix] Google Using Openmoko For gPhone?<br />
<br />
==== July 2007 ====<br />
* [http://www.pcworld.com/article/id,134987-pg,1/article.html PCWorld] Insider Info on the First Fully Open-Source Cell Phone<br />
* [http://blog.wired.com/monkeybites/2007/07/hands-on-with-t.html Wired Blog] Hands On with Openmoko: An early look at the hardware and software.<br />
* [http://www.economist.com/science/displaystory.cfm?story_id=9531007 Economist.com] Hello world: Avoiding punitive roaming charges abroad<br />
* [http://linuxdevices.com/news/NS7355980470.html linuxdevices.com] iPhone-like Linux phone ready for hackers<br />
* [http://www.heise.de/english/newsticker/news/92473 heise.de] "Free your phone": The Openmoko Project's Linux Smartphone now available<br />
* [http://blogs.zdnet.com/open-source/?p=1194 zdnet.com] Can Openmoko break the wireless monopoly?<br />
* [http://developers.slashdot.org/developers/07/07/09/0049249.shtml Slashdot] Open Source Linux Phone Goes On Sale<br />
* [http://www.engadget.com/2007/07/09/openmoko-neo-1973-and-advanced-dev-kit-finally-for-sale/ engadget.com] Openmoko Neo 1973 and Advanced dev kit finally for sale<br />
* [http://www.theglobeandmail.com/servlet/story/RTGAM.20070703.WBcyberia20070703161759/WBStory/WBcyberia/ Globe and Mail, Toronto] The Next Big Thing? (good overview; some favorable comparisons with iPhone).<br />
* [http://arstechnica.com/news.ars/post/20070710-developer-models-of-openmoko-open-source-smartphone-released.html arstechnica.com] Developer models of Openmoko open-source smartphone released<br />
* [http://www.boingboing.net/2007/07/09/openmoko_linuxbased_.html boingboing (Cory Doctorow)] Openmoko: Linux-based $300 open smartphone<br />
* [http://www.channelweb.co.uk/vnunet/news/2192036/first-open-source-mobile-phone channelweb.co.uk / CRN] Openmoko preps first open source mobile<br />
* [http://www.makezine.com/blog/archive/2007/07/openmoko_300_linuxpowered.html?CMP=OTC-0D6B48984890 MAKE:] blogged about it.<br />
* [http://www.theregister.co.uk/2007/07/09/neo_1973_launch/ The Register] Is your phone free?<br />
* [http://www.theinquirer.net/default.aspx?article=41147 The Inquirer] Linux phone goes on sale<br />
<br />
==== June 2007 ====<br />
* [http://fakesteve.blogspot.com/2007/06/freetards-are-trying-to-make-iphone.html Secret Diary of Steve Jobs] Freetards are trying to make an iPhone clone<br />
* [http://www.eweek.com/article2/0,1895,2152759,00.asp eweek.com] Openmoko: An iPhone Alternative for Developers? <br />
* [http://www.linuxdevices.com/news/NS8509737406.html&cid=0 linuxdevices.com] iPhone-like Linux phone delayed<br />
* [http://www.itweek.co.uk/vnunet/news/2192036/first-open-source-mobile-phone IT Week] "Openmoko preps first open source mobile" Confuses Phase 1 and Phase 2 features.<br />
* [http://www.vnunet.com/vnunet/news/2192036/first-open-source-mobile-phone vnunet.com] First open source mobile phone<br />
* [http://www.techeblog.com/index.php/tech-gadget/feature-5-cool-linux-powered-phones TechEBlog.com] A brief line-up of the 5 coolest Linux-powered phones.<br />
* [http://www.tectonic.co.za/view.php?id=1574 Tectonic.co.za] Open source phone plans September launch<br />
* [http://www.hothardware.com/image_popup.aspx?image=big_fic2.jpg&articleid=979&t=a hothardware.com] Openmoko<br />
* [http://www.texyt.com/FIC+Openmoko+$350+open+Linux+mobile+phone+launch+00100 Texyt.com] $350 open Linux mobile phone on target for September launch<br />
<br />
==== May 2007 ====<br />
* [http://blogs.sun.com/brewin/entry/fic_and_openmoko_thank_you blogs.SUN.com] "FIC and Openmoko - Thank You" Mentions the FIC phone used in the exciting JavaFX Mobile announcement, and says that "in most cases the Neo 1973 phone performed better" than other handsets.<br />
* [http://www.pikesoft.com/blog/index.php?itemid=174 PikeSoft.com] JavaFX Mobile: a new smartphone OS contender<br />
* [http://www.sfgate.com/cgi-bin/blogs/sfgate/detail?blogid=19&entry_id=16310 SFGate.com] Here comes the Sun Conference<br />
* [http://www.linuxdevices.com/news/NS7539760574.html LinuxDevices.com] Sun beams Linux/Java at mobile phones<br />
<br />
==== April 2007 ====<br />
* [http://www.palminfocenter.com/news/9371/openmoko-running-on-a-palm-tx/ Palm Infocenter] Openmoko running on a palm TX<br />
* [http://jaidev.info/home/blog/archives/2007/04/13/openmoko.html JaidevInfo] Openmoko<br />
* [http://www.wirelessweek.com/newsletter.aspx?id=137388 Wirelessweek.com] Democracy Hits the Mobile Phone<br />
* [http://elearner.edublogs.org/2007/04/11/technologies-is-that-a-word/ Edublogs.org] Technologies is that a word? <br />
* [http://www.linuxdevices.com/news/NS4777580627.html Linuxdevices.com] 200 million Linux phones to ship by 2012<br />
* [http://arstechnica.com/news.ars/post/20070415-palm-embracing-linux-in-the-hopes-of-being-relevant-again.html Ars Technica] Palm embracing Linux in the hopes of being relevant again] (Mentions Neo1973 in passing)<br />
<br />
==== March 2007 ====<br />
* [http://www.smartdevicecentral.com/article/Openmokos+Open+Source+Phone/202546_1.aspx smartdevicecentral.com] Openmoko's open source phone<br />
* [http://www.zdnetasia.com/news/communications/0,39044192,61996003,00.htm zdnet asia] Passing mention in an article on the Iphone.<br />
* [http://www.wikio.com/news/Sean+Moss-Pultz wikio.com] Sean Moss-Pultz News<br />
* [http://www.edparsons.com/?p=438 edparsons.com] iPhone chipping away at the walls<br />
* [http://blogs.pcworld.co.nz/pcworld/techsploder/2007/03/openmoko_makes_total_sense.html blogs.pcworld.co.nz] Openmoko makes total sense<br />
* [http://www.totalueberwachung.de/blog/articles/2007/03/08/neo1973-arrived totalueberwachung.de] Neo1973 arrived<br />
* [http://www.makuchaku.info/blog/im-gonna-get-this-one makuchaku.info] I'm gonna get this one<br />
* [http://www.kitenet.net/~joey/blog/entry/openmoko_and_n800.html kitenet.net] Openmoko and n800<br />
* [http://dominion.kabel.utwente.nl/koen/cms/the-neo1973-unboxed dominion.kabel.utwente.nl] The Neo1973 unboxed<br />
* [http://atulchitnis.net/diary/showentry/421 atulchitnis.net] An Openmoko Phone arrives<br />
* [http://blog.matthewgast.com/2007/03/03/good-luck-openmoko blog.matthewgast.com] Good luck Openmoko<br />
* [http://vaandoo.blogspot.com/2007/03/openmoko-neo1973-opensource-software.html vaandoo.blogspot.com] Openmoko Neo1973 opensource software<br />
* [http://www.linuxdevices.com/news/NS7653749655.html linuxdevices.com] Openmoko update; Neo1973 on sale in March<br />
* [http://www.ministryoftech.com/2007/03/05/the-5-hottest-phones-for-linux-fanatics/ ministryoftech.com] Brief line-up of the 5 hottest phones for Linux fans<br />
* [http://voxilla.com/soapvox/2007/03/01/industry-disruption-really-168 voxilla.com] Article about ETel Sean Moss-Pultz presentation<br />
* [http://blog.wired.com/gadgets/2007/03/eight_great_lin.html blog.wired.com] Gadget Lab: Eight Great Linux Smartphones<br />
* [http://gigaom.com/2007/03/01/openmoko-phone/ gigaom.com] Openmoko Open-Source Mobile, coming soon - Interview with Sean Moss-Pultz<br />
* [http://www.oreillynet.com/etel/blog/2007/03/openmoko_1.html www.oreillynet.com] ETel coverage<br />
* [http://gordoncook.net/wp/?p=146 gordoncook.net] Short history of Neo1973 and other stuff<br />
* [http://www.engadget.com/2007/03/03/openmoko-details-pricing-availability-for-neo1973/ engadget.com] Openmoko details pricing, availability for Neo1973<br />
* [http://www.uberpulse.com/us/2007/03/fic_wants_to_rewrite_the_rules_with_open_moko_mobile_phone.php www.uberpulse.com] Some images from ETel<br />
<br />
==== February 2007 ====<br />
* [http://www.scullen.ca/2007/02/15/forget-about-the-iphone-neo1973-is-far-more-exciting/ scullen.ca] Forget about the iPone, Neo1973 is far more exciting<br />
* [http://www.mobileread.com/forums/showpost.php?p=59124&postcount=4 mobileread.com] Show post<br />
* [http://www.pdasnews.com/articles/2568/1/ pdasnews.com] Linux-powered iPhone killer available online in March<br />
* [http://www.belutz.net/2007/02/05/openmoko/ belutz.net] Openmoko<br />
* [http://www.mail-archive.com/community@lists.openmoko.org/msg03686.html mail-archive.com] Openmoko community mail archive<br />
* [http://www.maclife.com/article/is_three_a_crowd_in_the_touch_screen_phone_arena maclife.com] Is there a crowd in the touch screen phone arena<br />
* [http://gopaultech.com/2007/02/fic-neo1973-linux-smartphone/ gopaultech.com] FIC Neo1973 Linux smartphone<br />
* [http://www.volweb.cz/horvitz/os-info/news-feb07-014.html volweb.cz] Open-source smartphone, with WiFi in version 2<br />
* [http://www.oreillynet.com/etel/blog/2007/02/etel_coverage_openmoko_opens_t.html oreillynet.com] ETel coverage Openmoko opens<br />
* [http://www.mobilewhack.com/openmoko-neo1973-open-source-phone/ mobilewhack.com] Openmoko Neo1973 open source phone<br />
* [http://www.engadget.com/2007/02/19/what-tech-would-the-presidents-rock-in-2007/ engadget.com] What tech would the presidents rock in 2007<br />
* [http://www.tuxmachines.org/node/13602 tuxmachines.org] What participation culture<br />
* [http://www.vanille-media.de/site/index.php/category/opensource/openmoko/ vanille-media.de] Opensource Openmoko<br />
* [http://www.joetech.com/2007/02/15/openmoko-open-source-cell-phone/ joetech.com] Openmoko open source cell phone<br />
* [http://www.makezine.com/blog/archive/2007/02/openmoko_open_s.html makezine.com] Openmoko open<br />
* [http://www.linuxdevices.com/news/NS9706477996.html linuxdevices.com] Announce of the Openembedded booth at FOSDEM in Brussels.<br />
* [http://www.linuxdevices.com/news/NS2657814070.html linuxdevices.com] Quick interview with Sean and some pictures<br />
* [http://gizmodo.com/gadgets/smartphones/first-look-the-antiiphone-openmokos-neo1973-236841.php gizmodo.com] Photos and comments on hardware and software<br />
* [http://www.onecompare.com/mobile-news/article-asp~aid~244~pub~56321102~story~openmoko-launch-the-official-portal-for-development-of-the-openmoko-platform onecompare.com] Short news article<br />
* [http://crunchgear.com/2007/02/15/openmokos-open-source-mobile-os crunchgear.com] Holding the phone upside down<br />
* [http://www.slashgear.com/openmoko-and-fic-neo1973-updates-153926.php slashgear.com] Video interview and many pictures<br />
* [http://www.djlosch.com/article_Comparison%3A_iPhone_vs_A1200_vs_Neo1973 djlosch.com] Article comparing the Neo to the iPhone and A1200<br />
* [http://popsci.typepad.com/popsci/2007/02/up_close_and_pe.html popsci.typepad.com] Screenshot of Linux booting on the Neo<br />
* [http://video.google.de/videoplay?docid=-3742589179435830945&q=Openmoko video.google.com] Presentation of Openmoko at the FOSDEM<br />
* [http://www.manilastandardtoday.com/?page=business6_feb27_2007 manilastandardtoday.com] Tale of two phones<br />
* [http://blog.printf.net/articles/2007/02/22/unboxing-the-openmoko-phone blog.printf.net] OLPC and older Neo1973.<br />
* [http://mako.cc/copyrighteous/freesoftware/20070228-00.html mako.cc] OLPC and older Neo1973 again.<br />
* [http://www.maclife.com/article/is_three_a_crowd_in_the_touch_screen_phone_arena MacLife] Is Three a Crowd among Touch-Screen Phones?<br />
* [http://www.linuxjournal.com/article/9489#mpart5 Linux Journal] A White Box Phone<br />
<br />
==== January 2007 ====<br />
* [http://blogs.ft.com/techblog/2007/01/openmoko_harks_.html blogs.ft.com] Openmoko harks back to hello moto<br />
* [http://opensource.sfsu.edu/node/258 opensource.sfsu.edu] Can you hear me now?<br />
* [http://losca.blogspot.com/2007/01/maemo-nokia-n800-has-competitor-in.html losca.blogspot.com] Maemo Nokia n800 has competitor in openness - Openmoko<br />
* [http://21talks.net/voip/openmoko 21talks.net] Openmoko: Not as sexy as the iPhone, but it’s a Linux phone<br />
* [http://www.linuxinfusion.com/openmoko-schedule-announced linuxinfusion.com] Openmoko schedule announced<br />
* [http://users.livejournal.com/_paladine_/tag/smartphone users.livjournal.com] The Worlds First Opensource Linux Smartphone<br />
* [http://www.nungee.com/2007/01/25/openmoko/ nungee.com] Openmoko<br />
* [http://www.sda-asia.com/sda/features/psecom,id,880,srn,2,channel,developer,nodeid,21,_language,Singapore.html sda-asia.com] Openmoko Offers Open-source Smart phone T<br />
* [http://www.regdeveloper.co.uk/2007/01/15/open_phone/ regdeveloper.co.uk] Open Phone<br />
* [http://www.product-reviews.net/2007/01/17/fic-neo1973-smartphone-open-source-phone/ product-reviews.net] FIC Neo1973 smartphone open source phone<br />
* [http://gizmodo.com/gadgets/smartphones/openmoko-smartphone-did-they-have-a-time-machine-or-what-229243.php gizmodo.com] Openmoko smartphone did they have a time machine or what<br />
* [http://www.oreillynet.com/conferences/blog/2007/01/openmoko_workshop_added_to_ete.html oreillynet.com] Openmoko workshop added to ETel<br />
* [http://www.gadgetell.com/2007/01/openmoko-gets-interviewed-about-new-open-source-fic-neo1973/ gadgetell.com] Openmoko gets interviewed about new open source FIC Neo1973<br />
* [http://www.slashgear.com/openmoko-interface-im-loving-it-173496.php slashgear.com] Openmoko interface I'm loving it<br />
* [http://www.gadgetorama.com/news/news_details.php?gorid=2008 gadgetorama.com] Openmoko news details<br />
* [http://tech.cybernetnews.com/2007/01/17/openmoko-vs-iphone-did-apple-copy/ tech.cybernetnews.com] Openmoko vs iPhone did Apple copy<br />
* [http://techtrails.blogspot.com/2007/01/open-phones-with-open-moko-while.html techtrails.blogspot.com] Open phones with Openmoko while<br />
* [http://blogger.xs4all.nl/jurjen1/archive/2007/01/17/174341.aspx bloger.xs4all.nl] Openmoko open source mobile phone<br />
* [http://www.ringnokia.com/2007/01/i_am_highly_cur.html ringnokia.com] I'm highly curious<br />
* [http://www.oreillynet.com/etel/blog/2007/01/iclone_1.html oreillynet.com] iClone<br />
* [http://forums.scotsnewsletter.com/index.php?showtopic=17685 forums.scotsnewsletter.com] Show topic<br />
* [http://understandinglimited.com/2007/01/15/iphone/ understandinglimited.com] iPhone and Openmoko<br />
* [http://robertogaloppini.net/2007/01/12/openmoko-the-integrated-os-mobile-communications-platform-2/ robertogaloppini.net] Openmoko the intergrated OS mobile communications platform<br />
* [http://www.funambol.com/blog/capo/2007/01/apple-please-do-not-forget-developers.html funambol.com] Apple please do not forget developers<br />
* [http://chopey.blogspot.com/2007/01/iphone-or-not-to-iphone.html chopey.blogspot.com] iPhone or not to iPhone<br />
* [http://opendotdotdot.blogspot.com/2007/01/openmoko.html opendotdotdot.blogspot.com] Openmoko<br />
* [http://www.e-pcmag.gr/forum/index.php?showtopic=19505 e-pcmag.gr] Show topic<br />
* [http://www.costpernews.com/2007/01/12/anything-you-can-do-we-can-do-better/ costpernews.com] Anything you can do we can do better<br />
* [http://www.tectonic.co.za/view.php?id=1321 tectonic.co.za] iPhone vs Openmoko - the Open Alternative<br />
* [http://lwn.net/Articles/217020/rss lwn.net] An Openmoko update<br />
* [http://www.networkworld.com/news/2007/010907-moss-pultz.html networkworld.com] Q&A Building a new open source phone platform<br />
* [http://www.networkcomputing.com/showArticle.jhtml?articleID=196802226 networkcomputing.com] Startup Promises First Linux Smartphone Based On Open Standards<br />
* [http://www.osweekly.com/index.php?option=com_content&task=view&id=2420&Itemid=449 osweekly.com] Mobile Devices Adopt Open Source<br />
* [http://www.linuxdevices.com/news/NS8591201260.html linuxdevices.com] Linux phone market open up?<br />
* [http://www.pcmag.com/article2/0,1895,2080727,00.asp pcmag.com] Cell phone open up<br />
* [http://sonyericssonz558i.blogurple.com/2007/01/06/23/ sonyericssonz558i.blogurple.com] Sony Ericsson Z558i<br />
* [http://www.sannes.org/?p=5 sannes.org] An Open mobile phone that does what you want<br />
* [http://popsci.typepad.com/ces2007/2007/01/opensource_stri.html Popsci.com] Open Source Strikes Again<br />
* [http://gizmodo.com/gadgets/smartphones/openmoko-smartphone-did-they-have-a-time-machine-or-what-229243.php Gizmodo.com] Openmoko interface compared to iPhone<br />
* [http://www.linuxjournal.com/xstatic/abstracts/upfront Linux Journal] Doc Searls in the feb 2007 issue<br />
* [http://www.osdir.com/Article9642.phtml OSDir.com] Mobile Linux for the Mobile Fan] -> [http://www.madpenguin.org/cms/?m=show&id=7710 MadPenguin] Mobile Linux for the Mobile Fan<br />
* [http://www.usnews.com/usnews/biztech/davesdownload/archive/070112/a_populist_challenge_to_apples.htm US News] A Populist Challenge to Apple's iPhone<br />
* [http://www.tectonic.co.za/view.php?id=1321 tectonic.co.za] iPhone vs Openmoko: The open alternative<br />
* [http://www.informationweek.com/news/showArticle.jhtml?articleID=196802206&subSection=All+Stories InformationWeek] Startup Promises First Linux Smartphone Based On Open Standards<br />
* [http://www.theregister.co.uk/2007/01/15/open_phone/ The Register] Open Phones with Open Moko<br />
* [http://techreport.com/onearticle.x/11589 The Tech Report] Openmoko offers open-source smart phone<br />
* [http://blogs.ft.com/techblog/2007/01/openmoko_harks_.html Financial Times] Openmoko harks back to Hello Moto<br />
* [http://hardware.slashdot.org/article.pl?sid=07/01/20/1551200 Slashdot] Openmoko Schedule Announced<br />
* [http://www.youtube.com/watch?v=jRvtAAXTIlg Youtube] Interview with Sean Moss-Pultz ([http://www.monoploid.be/dl/openmoko_sean_interview.ogm mirror in Ogg format])<br />
* [http://www.libervis.com/article/forget_iphone_hail_openmoko_the_true_revolution Libervis.com] Forget iPhone, hail Openmoko, the true revolution<br />
* [http://gizmodo.com/gadgets/smartphones/sizemodo-iphone-vs-openmoko-neo1073-229294.php Gizmodo]iPhone vs. Openmoko Neo1973] (please, don't mind the typo i n the title)<br />
<br />
==== December 2006 ====<br />
* [http://www.pikesoft.com/blog/index.php?itemid=133 pikesoft.com] Cheap, totally open Linux phone will ship next month<br />
* [http://www.cdrinfo.com/Sections/News/Details.aspx?NewsId=19254 cdrinfo.com] FIC to release Linux based Smartphone<br />
<br />
==== November 2006 ====<br />
* [http://www.ministryoftech.com/2006/11/09/fic-neo1973-smartphone-with-linux-based-openmoko-open-source-platform/ ministryoftech.com] FIC Neo1973 smartphone with linux-based Openmoko open source platform<br />
* [http://www.mobiletechnews.com/info/2006/11/09/124614.html mobiletechnews.com] Openmoko Linux mobile platform and Neo1973 smartphone announced<br />
* [http://news.softpedia.com/news/FIC-Neo1973-for-all-the-Linux-Lovers-out-There-40344.shtml news.softpedia.com] FIC Neo1973 for all the Linux lovers out there<br />
* [http://www.openembedded.org/openmoko-fic-choosing-openembedded openembedded.org] Openmoko FIC choosing openembedded<br />
* [http://news.com.com/2300-1037_3-6134795-1.html news.com.com] FIC's Linux handset<br />
* [http://www.slashphone.com/77/5784.html slashphone.com] Openmoko Announces Open Source Mobile Communications Platform <br />
* [http://www.arm.com/iqonline/news/marketnews/15616.html arm.com] Open Linux Based, ARM Powered Mobile In Wings<br />
* [http://news.com.com/Second+open+Linux+handset+unveiled/2100-1039_3-6133974.html news.com.tw] Second open Linux handset unveiled<br />
* [http://www.infoworld.com/article/06/11/08/HNlinuxphone_1.html?COMMERCIAL%20LINUX infoworld.com] FIC debuts open Linux-based smartphone <br />
* [http://www.michaeldolan.com/431 michaeldolan.com] A must have: Openmoko cell phone with GPS and...apt-get<br />
* [http://nandz.blogspot.com/2006/11/my-dream-phone.html nandz.blogspot.com] My dream phone<br />
* [http://www.linuxdevices.com/news/NS2986976174.html linuxdevices.com] Cheap, hackable Linux smartphone due soon<br />
* [http://www.linuxdevices.com/news/NS7056478804.html linuxdevices.com] First OpenmoKo phone taps dual-licensed SyncML stack<br />
* [http://lwn.net/Articles/208298/ lwn.net] The Openmoko open phone<br />
* [http://www.theinquirer.net/default.aspx?article=35590 theinquirer.net] A truly open Linux phone with GPS debuts<br />
<br />
=== German ===<br />
==== November ====<br />
* [http://www.heise.de/newsticker/meldung/98489 heise.de: Das GPhone ist ein Android] GPhone System "wildert in den Gefilden vergleichbarer Initiativen wie Openmoko"<br />
<br />
==== September ====<br />
* [http://futurezone.orf.at/produkte/stories/219038/ futurzone@orf.at] "Und jetzt: Befreien Sie Ihr Handy."<br />
* [http://www.pro-linux.de/news/2007/11704.html Pro-Linux] Openmoko für den Massenmarkt erst an Weihnachten<br />
<br />
==== August 2007 ====<br />
* [http://www.golem.de/0708/54256.html golem.de] - Neues GUI für Open-Source-Handy Neo1973<br />
* [http://www.heise.de/mobil/newsticker/meldung/94724 heise mobil] - Offene Smartphone-Plattform mit neuem Look<br />
<br />
==== July 2007 ====<br />
* [http://lists.openmoko.org/pipermail/community/attachments/20070721/be55235c/CIMG1129_small-0001.jpg Kurier] - Handy Individuell<br />
* [http://futurezone.orf.at/produkte/stories/206048/ futurezone.ORF.at] - Anti-iPhone geht an den Start<br />
* [http://www.zdnet.de/news/hardware/0,39023109,39156101,00.htm zdnet.de] - Open-Source-Iphone wird mit Hackertools ausgeliefert<br />
* [http://www.heise.de/newsticker/meldung/92393 heise.de] - "Free your phone": Linux-Smartphone des Openmoko-Projekts verfügbar<br />
* [http://www.spiegel.de/netzwelt/mobil/0,1518,493595,00.html spiegel.de] - Linux statt iPhone: Freiheit fürs Handy<br />
<br />
==== June 2007 ====<br />
* [http://www.golem.de/0706/53172.html golem.de] - Linux-Smartphone Openmoko ab Juli 2007 zu haben <br />
* [http://www.heise.de/newsticker/meldung/91868 heise.de] - Offenes Linux-Smartphone Neo 1973 macht Fortschritte<br />
* [http://www.winfuture.de/news,32641.html winfuture.de] - Open-Source-Handy Neo1973 ab Juli bzw. Oktober<br />
* [http://www.pro-linux.de/news/2007/11385.html pro-linux.de] - Openmoko wird zum Unternehmen<br />
* [http://de.theinquirer.net/2007/06/14/das_erste_openmoko_kommt.html the inquirer] - Das erste OpenMOKO kommt<br />
<br />
==== April 2007 ====<br />
* [http://www.pro-linux.de/news/2007/11133.html pro-linux] - Openmoko produziert erste Muster<br />
* [http://www.golem.de/0704/51970.html golem.de] - Open-Source-Handy vor Produktionsbeginn<br />
<br />
==== March 2007 ====<br />
* [http://chaosradio.ccc.de/cre042.html Chaosradio Express] - Das neue Projekt zur Entwicklung eines Telefons mit freier Software<br />
* [http://www.pro-linux.de/news/2007/10966.html pro-linux] - Openmoko sucht Unterstützung<br />
<br />
==== February 2007 ====<br />
* [http://www.digital-living-magazin.de/index.php?pid=17&art=2050&cid=DLnewsletter digital-living-magazin.de] - Linux erobert Mobilfunkmarkt<br />
* [http://www.heise.de/tr/artikel/85138 Technology Review] - Open-Source-Handy, nächster Versuch<br />
* [http://www.pro-linux.de/news/2007/10833.html pro-linux] - Openmoko-Quellcode angekündigt<br />
* [http://www.heise.de/newsticker/meldung/85354 heise online] - Openmoko: Linux-Plattform für Handys freigegeben<br />
* [http://www.mobile2day.de/news/news_details.html?nd_ref=6870&n_multi=0&nf_id=0&nt_id=0&f_date_m=01&f_date_y=2007&t_date_m=04&t_date_y=2007&from=archive Mobile2Day] - Openmoko bringt Details zum Neo1973<br />
<br />
==== November 2006 ====<br />
<br />
* [http://golem.de/0611/48824.html golem.de] - Openmoko kündigt Open-Source-Handy an<br />
* [http://www.heise.de/newsticker/meldung/80714 heise online] - Smartphone mit offener Linux-Plattform<br />
* [http://www.pro-linux.de/news/2006/10448.html pro-linux] - Offenes Linux-Smartphone »Openmoko« für Januar 2007 angekündigt<br />
<br />
=== Scandinavian ===<br />
<br />
<br />
*expressen.se, 15. aug 2008, [http://www.expressen.se/prylar/1.1266066/mobilen-du-kan-bygga-om-sjalv Mobilen du kan bygga om själv] (the customizable phone)<br />
*computerworld.dk, 4. juli 2008, [http://www.computerworld.dk/art/46877?a=block&i=205&pos=8&bpos=999 Anti-iPhonen Openmoko på gaden i dag].<br />
*version2.dk, 4. jul 2008, [http://www.version2.dk/artikel/7825 Galleri: Open source-phonen Openmoko Neo Free Runner].<br />
*version2.dk, 4. jul 2008, [http://www.version2.dk/artikel/7823 Linux-phonen vil også med i det smarte selskab].<br />
*newz.dk, 4. jul. 2008, [http://newz.dk/openmoko-lancerer-linuxtelefonen-neo-freerunner Openmoko lancerer linuxtelefonen Neo FreeRunner].<br />
*dr.dk, 3. juli 2008, [http://blogs.dr.dk/blogs/harddisken/archive/2008/07/03/mobilernes-kamp.aspx Harddisken: Mobilernes kamp!]<br />
*silenzio.dk, 4. maj (en. May), 2008, [http://silenzio.dk/gadgets/2008/05/openmoko-neo-freerunner/ Openmoko - Neo FreeRunner].<br />
* Ing.dk, 11. jul. 2007, [http://ing.dk/artikel/79906 Linux-mobil skræddersyet til hackere].<br />
* Amobil.no, 6. jul. 2007, [http://www.amobil.no/artikkel/mobiltelefoner/antikrist-mobilen_blir_heftigere/41042 En oppgradert utgave av Linux-mobilen Neo1973 er på vei].<br />
* Amobil.no, 7. jun. 2007, [http://www.amobil.no/sniktitt/mobiltelefoner/den_folsomme_linux-mobilen/40176 Sniktitt: Den følsomme Linux-mobilen].<br />
* Amobil.no, 6. jun. 2007, [http://www.amobil.no/artikkel/markedsutvikling/linux-mobilen_er_i_rute/40138 Linux-mobilen er i rute].<br />
*linuxforum.dk, 1. March 2007, [http://www.linuxforum.dk/2007/program/saturday/Martin_Hansen.shtml Openmoko - Verdens første 100% åbne mobiltelefon] med Martin Hansen & Ole Tange.<br />
* Amobil.no, 16. feb. 2007, [http://www.amobil.no/nyhet/mobiltelefoner/openmoko_klart_for_verden/36554 Openmoko klart for verden].<br />
*newz.dk, 15. feb. 2007, [http://newz.dk/openmoko-gjort-offentligt-tilgaengelig Openmoko gjort offentligt tilgængelig].<br />
* nyteknik.se, 22. jan. 2007, [http://www.nyteknik.se/nyheter/it_telekom/mobiltele/article42114.ece Snart är den öppna Linuxtelefonen här] (Swedish) (Translation: this article states free release to selected developers Feb 11, commercial release to developers March 11, and main release to market Sep 11. See also [http://lists.openmoko.org/pipermail/announce/2007-January/000000.html])<br />
<br />
=== French ===<br />
* [http://linuxfr.org/2006/11/08/21596.html LinuxFR] Openmoko : sortie en janvier d'un téléphone-GPS enfin libre!<br />
<br />
=== Chinese ===<br />
<br />
* [http://tw.news.yahoo.com/article/url/d/a/080215/5/tinm.html CNA] Openmoko Education in Taiwan<br />
* [http://futurenotyet.blogspot.com/2008/01/openmoko.html Future Not Yet Blog] Visit Openmoko & Openmoko is Hiring<br />
* [http://tech.digitimes.com.tw/ShowNews.aspx?zCatId=A2O&zNotesDocId=0000079427_A6OLFT3HUX3IY4B646C0Z Digitimes] Open Source Mobile Revolution: Openmoko Technology & Concepts Analysis<br />
* [http://marrtw.blogspot.com/2007/11/intro-to-openmoko.html Marr's Weblog] Intro to Openmoko. Also mention OpenLab.<br />
* [http://1-apple.com.tw/apple/index.cfm?Fuseaction=Article&Sec_ID=8&ShowDate=20071119&NewsType=twapple&Loc=TP&Art_ID=4009959 1-Apple Daily News] FIC/Openmoko provide 100% open source mobile communication platform.<br />
* [http://www.pconline.com.cn/mobile/news/hgxz/0711/1157957.html PConline China] Neo 1973 test report.<br />
* [http://news.sina.com.tw/tech/sinacn/cn/2007-11-16/110338206084.shtml Sina Taiwan] Neo 1973 test report.<br />
* [http://news.oss.tw/node/6363 News.Oss.Tw] Openmoko OpenLab Opening<br />
* [http://www.digitimes.com.tw/n/article.asp?id=0000072911_B8M11RL8U70UDGF2BY10X DigitTimes Taiwan] News about Openmoko OpenLab Opening and Neo1973.<br />
* [http://openmoko.wordpress.com/2007/06/21/openmoko-%E8%88%87-iphone-%E6%AF%94%E8%BC%83%E4%B8%80/ wordpress.com] Comparison between Openmoko and iPhone<br />
* [http://chinese.engadget.com/2007/06/11/computex-2007-openmoko-neo-1973-linux/ chinese engadget.com] Openmoko Neo1973 Linux Smartphone<br />
* [http://people.debian.org.tw/~chihchun/2007/05/25/talk-of-openmoko-is-online/ debian.org.tw] Video of Openmoko at TOSSUG in Taipei<br />
* [http://people.debian.org.tw/~chihchun/2007/05/17/openmoko-at-tossug/ debian.org.tw] Openmoko at TOSSUG<br />
* [http://magicdesign.blogspot.com/2007/05/free-your-phoneopenmoko.html MagicDesign] Free your phone Openmoko<br />
* [http://people.debian.org.tw/~chihchun/2007/04/30/have-fun-with-openmokoneo1973/ Debian.org.tw] Have fun with Openmoko Neo1973<br />
* [http://orzlab.blogspot.com/ Orzlab] When Java meets Openmoko<br />
* [http://blog.footoo.org/?p=115 FooToo.org] Install Openmoko Emulator<br />
* [http://www.jollen.org/blog/2007/01/openmoko_announce.html Jollen.org] Openmoko Kick-Off<br />
* [http://zh.wikipedia.org/wiki/Openmoko Wikipedia.org] Openmoko Chinese Wiki<br />
* [http://tw.myblog.yahoo.com/champ_yen/article?mid=211&prev=212&next=-1 Yahoo.com.tw] Forget about iPhone, Hail Openmoko <br />
* [http://www.jollen.org/blog/2006/11/mobile_20_openmoko_linux_smart.html Jollen.org] Openmoko Linux Smartphone<br />
* [http://blog.roodo.com/ystuan/archives/2733869.html Roodo.com] Openmoko<br />
<br />
=== Polish ===<br />
==== May 2007 ====<br />
* [http://www.studencka.pl/artykuly.php?AID=770 Gazeta Studencka] (Students Newspaper) "Cellphones of all shapes, unite!" - Openmoko overview by Krzysztof Kajkowski, "free software" not mentioned in the text.<br />
<br />
=== Japanese ===<br />
<br />
* [http://blog.pasonatech.co.jp/hibi/4079.html pasonatech.co.jp] iPhoneキラー?:オープンソース精神なopenmoko携帯がUSで発売<br />
* [http://journal.mycom.co.jp/articles/2007/06/06/computex04/index.html journal. mycom.com.jp] Computex Taipei 2007<br />
<br />
<br />
=== Italian ===<br />
<br />
==== July 2007 ====<br />
* [http://www.corriere.it/Primo_Piano/Scienze_e_Tecnologie/2007/07_Luglio/10/neo1973_telefonino.shtml corriere.it] L'anti iPhone: Neo 1973, il cellulare fai da te<br />
* [http://punto-informatico.it/p.aspx?id=2035879 Punto Informatico] Lo smartphone touch-screen è open source<br />
<br />
<br />
=== Dutch ===<br />
<br />
==== September 2007 ====<br />
*[http://www.pocketinfo.nl/nieuws/smartphones/9073/de-stand-van-zaken-rond-openmoko.html pocketinfo.nl] De stand van zaken rond Openmoko.<br />
*[http://life.tweakers.net/nieuws/49288/Productieversie-Openmoko-telefoon-nog-dit-jaar-leverbaar.html tweakers.net] Productieversie Openmoko-telefoon nog dit jaar<br />
<br />
==== July 2007 ====<br />
*[http://www.techzine.nl/nieuws/12929/Opensource-OS-voor-telefoons-geintroduceerd.html techzine.nl] Opensource OS voor telefoons geïntroduceerd<br />
*[http://core.tweakers.net/nieuws/48335/Open-Linux-smartphone-in-de-verkoop.html tweakers.net] Open Linux-smartphone in de verkoop<br />
*[http://www.opensourcenieuws.nl/index.php/content/view/4148/54/ opensourcenieuws.nl] Openmoko platform en de Openmoko Neo1973 gelanceerd.<br />
*[http://www.gadgetgarden.nl/archives/2007/07/fic_linux_openm.php] FIC Linux Openmoko Smartphone: zoals jij wilt!<br />
<br />
==== March 2007 ====<br />
*[http://www.bits-chips.nl/artikel/art_view.asp?ac=view&art_id=9682 bits-chips.nl]Open-source-ontwikkelaars snakken naar open mobieltje.<br />
<br />
==== February 2007 ====<br />
*[http://www.telecomwereld.nl/n0001717.htm telecomwereld.nl] Neo1973 eerste smartphone voor Openmoko Linux <br />
*[http://www.opensourcenieuws.nl/index.php/content/view/3914/54/ opensourcenieuws.nl] Openmoko Iphone met Linux <br />
*[http://www.zdnet.nl/news.cfm?id=65618&mxp=201 zdnet.nl] iPhone-concurrent draait Linux<br />
*[http://www.bits-chips.nl/artikel/art_view.asp?ac=view&art_id=9210 bits-chips.nl] Mobieltjesmakers zoeken openheid<br />
<br />
==== November 2006 ====<br />
*[http://www.hollandopen.nl/article.jsp?nr=3554 hollandopen.nl] Openmoko: Open source platform voor mobiele telefoons<br />
*[http://www.bits-chips.nl/artikel/art_view.asp?ac=view&art_id=8540 bits-chips.nl] Openmoko moet mobieltjes openen voor ontwikkelaars<br />
<br />
{{Languages|Press_Coverage}}<br />
[[Category:Community]]<br />
[[Category:Event]]<br />
[[Category:Openmoko]]</div>DolfjeBot1http://openmoko.org/wiki/BackupBackup2008-08-31T12:56:03Z<p>DolfjeBot1: Replacing 'Freerunner' with 'FreeRunner'</p>
<hr />
<div>== Backing up just /home/root ==<br />
<br />
To backup the home folder (all your files personal files in theory).<br />
<br />
From the desktop pc run:<br />
<br />
ssh root@phone 'tar -cpz /home/root' > moko-home-`date +%Y%m%d-%H%M%S`.tar.gz<br />
<br />
Where phone is the ip address of your phone (192.168.0.202).<br />
<br />
Personally I added an entry to /etc/hosts so the above works for me. I also added the desktop key to /home/root/.ssh/authorized_keys on the phone as per the instructions in [[USB_Networking#SSH_Keys]].<br />
<br />
If you want to check what is in the backup, run the following, replacing the filename with what was just created.<br />
<br />
tar -tzf moko-home-20080802-203108.tar.gz | less<br />
<br />
[http://timwise.wikispaces.com/my+neo+freerunner reference]<br />
<br />
== Backing up everything ==<br />
<br />
You may either :<br />
* Backup the flash contents, in order to be able to restore (see bellow)<br />
* or move the system to SD to be able to boot it from SD in case of need. See [[Moving current system from flash to SD]]<br />
<br />
=== Backing-up flash images ===<br />
<br />
You will need the [[Dfu-util]] to make a backup of your existing image.<br />
<br />
As when [[Flashing_the_Neo_FreeRunner|flashing]], you will need to be in [[Booting_the_Neo_FreeRunner#Log_into_U-Boot_in_the_NOR_Flash|U-Boot in the NOR Flash]]. Log into the NOR uBoot menu and select ''Set console to USB'' (for NRF just stay in NOR uBoot menu, do not select or enter anything). Now you will be able to flash, make backups of your FreeRunner or query the FreeRunner with [[Dfu-util|dfu-util]]. Backup is fairly slow; it took over ten minutes to back up a 247 MB rootfs.<br />
<br />
It is important that you connect the USB cable directly from your computer to your phone. If there is a hub between them, backup (and flashing) will mostly likely fail.<br />
<br />
{{note|On a Windows host, omit the "./" or "sudo ./" that precedes the commands listed on this page}}<br />
<br />
<pre><br />
sudo ./dfu-util -a kernel -R -U good-kernel.bin<br />
sudo ./dfu-util -a rootfs -R -U good-rootfs.jffs2<br />
sudo ./dfu-util -a splash -R -U good-splash.bin<br />
sudo ./dfu-util -a u-boot -R -U good-u-boot.bin<br />
sudo ./dfu-util -a u-boot_env -R -U good-u-boot_env.bin<br />
</pre><br />
<br />
Here is what a successful dfu-util backup run looks like:<br />
<br />
on the host PC:<br />
<pre><br />
$ sudo ./dfu-util -a kernel -R -U good-kernel.img<br />
dfu-util - (C) 2007 by Openmoko Inc.<br />
This program is Free Software and has ABSOLUTELY NO WARRANTY<br />
<br />
Opening USB Device 0x0000:0x0000...<br />
Claiming USB DFU Runtime Interface...<br />
Determining device status: state = appIDLE, status = 0<br />
Device really in Runtime Mode, send DFU detach request...<br />
Resetting USB...<br />
Opening USB Device...<br />
Found Runtime: [0x1d50:0x5119] devnum=12, cfg=0, intf=0, alt=3, name="kernel"<br />
Claiming USB DFU Interface...<br />
Setting Alternate Setting ...<br />
Determining device status: state = dfuIDLE, status = 0<br />
dfuIDLE, continuing<br />
Transfer Size = 0x1000<br />
Resetting USB to switch back to runtime mode<br />
</pre><br />
<br />
on the FreeRunner:<br />
<pre><br />
DFU: Switching to DFU Mode<br />
DEVICE_CONFIGURED: 1<br />
Starting DFU Upload of partition 'kernel'<br />
</pre><br />
<br />
A failed run of dfu-util looks like this:<br />
<br />
dfu-util - (C) 2007 by Openmoko Inc.<br />
This program is Free Software and has ABSOLUTELY NO WARRANTY<br />
<br />
Opening USB Device 0x0000:0x0000...<br />
Claiming USB DFU Runtime Interface... <br />
Determining device status: state = appIDLE, status = 0<br />
Device really in Runtime Mode, send DFU detach request...<br />
Resetting USB... <br />
Opening USB Device...<br />
Found Runtime: [0x1d50:0x5119] devnum=20, cfg=0, intf=0, alt=6, name="rootfs"<br />
Claiming USB DFU Interface...<br />
Setting Alternate Setting ...<br />
Determining device status: state = dfuIDLE, status = 0<br />
dfuIDLE, continuing<br />
Transfer Size = 0x1000<br />
dfu_upload error -110<br />
<br />
And shows errors demsg like this:<br />
usb 5-2: usbfs: USBDEVFS_CONTROL failed cmd dfu-util rqt 161 rq 2 len 4096 ret -110<br />
<br />
==Backup Scripts==<br />
<br />
If you plan on backing up frequently, using a script will simplify the process:<br />
<br />
===Simple backup script===<br />
<br />
This script works well if you want to configure it to backup always the same device.<br />
<br />
<pre><br />
#!/bin/sh<br />
#<br />
# Back up all partitions of the phone to a backup directory,<br />
# adding today's date to the saved filenames.<br />
<br />
DATE=`date +%Y-%m-%d`<br />
DFU=./dfu-util<br />
BACKUP_DIR=bak/<br />
<br />
${DFU} -a kernel -R -U ${BACKUP_DIR}kernel-${DATE}.bin<br />
${DFU} -a rootfs -R -U ${BACKUP_DIR}rootfs-${DATE}.jffs2<br />
${DFU} -a splash -R -U ${BACKUP_DIR}splash-${DATE}.bin<br />
${DFU} -a u-boot -R -U ${BACKUP_DIR}u-boot-${DATE}.bin<br />
${DFU} -a u-boot_env -R -U ${BACKUP_DIR}u-boot_env-${DATE}.bin<br />
</pre><br />
<br />
===Interactive script===<br />
<br />
This script is based on the above "Simple backup script" (by unknown). It does the backup of what you want and choose promting you for choices. Enjoy it! test it! contribute! You can find us at /server irc.freenode.net /j #openmoko and we'll be pleased to accept you help (ideas || code). <br />
<br />
NOTE that the script works for me(tm) but it still needs some love. especially on traps and catches for wrong choices.<br />
<br />
<pre><br />
#!/bin/bash<br />
<br />
#############################################################################################################<br />
## ##<br />
## This script is Free Software is licensed under the GPLv3 and has ABSOLUTELY NO WARRANTY ##<br />
## you can find and read the complete version of the GPLv3 @ http://www.gnu.org/licenses/gpl.html ##<br />
## ##<br />
## Q: what does this script do? ##<br />
## A: the script back up all partitions of the phone to a backup directory, interactively, ## <br />
## adding today's date to the saved filenames. ##<br />
## ##<br />
## IMPORTANT:!!! REMEMBER TO RUN THIS SCRIPT AS ROOT SINCE dfu-util HAS TO BE USED AS ROOT!!! ##<br />
## ##<br />
## based on the orginal simple backup script at http://wiki.openmoko.org/wiki/Pre-Flash_Backup ##<br />
## ##<br />
## this version has been conceived and written by cga, x77686d, Infoport, jomat at /server irc.freenode.net##<br />
## /j #openmoko,#bash and my collegue aubba @ work. ##<br />
## ##<br />
## for any suggestions and contributions contact cga (or one of the above) in the #openmoko channel ##<br />
## ##<br />
#############################################################################################################<br />
<br />
## let's roll!!<br />
<br />
## sets the date format for the date in the backup file, change accordingly to your local custom if you need<br />
DATE=`date +%d-%m-%Y`<br />
<br />
## here the scripts try to find the dfu-util binary and set it as the DFU var:<br />
if which dfu-util >/dev/null ; then<br />
echo<br />
echo "dfu-util found in your path"<br />
echo<br />
## 1 the function use this if you placed/linked dfu-util in your $PATH<br />
DFU=dfu-util<br />
<br />
elif ls dfu-util >/dev/null ; then<br />
echo<br />
echo "dfu-util found in current directory" <br />
echo<br />
## or 2 use following line if dfu-util is placed in the same directory where you run the script<br />
DFU=./dfu-util<br />
<br />
else<br />
## or 3 if the script doesn't find dfu-util shows the link for installing it and exit<br />
echo<br />
echo "dfu-util NOT found! install and use howto @ http://wiki.openmoko.org/wiki/Dfu-util"<br />
echo<br />
exit 1<br />
fi<br />
<br />
## here we get the hex code for devices found with dfu-util --list <br />
## the hex code is grabbed and the name of the device is shown accordingly and you are prompetd to chose the right one:<br />
echo<br />
echo 'these are the devices i found:' <br />
echo<br />
for device in `${DFU} --list | grep 0x | cut -f3 -d' ' | tr -d '[]'` ; do<br />
if [ "$device" == '0x1457:0x5119' ] ; then<br />
echo 'Neo 1973'<br />
elif [ "$device" == '0x1d50:0x5119' ] ; then<br />
echo "Neo FreeRunner"<br />
else<br />
echo 'other device found, DO NOT use dfu-util on this!!! it might bork it...'<br />
exit 1<br />
fi<br />
done | nl<br />
echo<br />
echo 'choose the device to backup:' <br />
echo<br />
read selection<br />
HEX=$(${DFU} --list | grep 0x | head -n $selection | tail -1 | cut -f3 -d' ' | tr -d '[]') <br />
<br />
## use the built-in read command to ask you and use the directory for the backup<br />
while [ -z "$BACKUP_DIR" ] ; do<br />
echo<br />
read -e -p $"enter the directory for the backup:" BACKUP_DIR<br />
echo<br />
<br />
## chek wether the dir exist and proceed, else create it and proceed.<br />
if [ ! -d "$BACKUP_DIR" ] ; then<br />
echo<br />
echo -n "$BACKUP_DIR does not exist, create it? [Y/n] "<br />
echo<br />
read CREATE_DIR<br />
if [ x"$CREATE_DIR" = xy -o x"$CREATE_DIR" = xY -o -z "$CREATE_DIR" ] ; then<br />
mkdir -p -v "${BACKUP_DIR}"<br />
else<br />
BACKUP_DIR=<br />
fi<br />
fi<br />
done<br />
<br />
## here you get prompted to chose the backup you want, you can backup single files or all of them.<br />
echo<br />
echo 'choose the component to backup from the list:'<br />
echo<br />
<br />
select howto in kernel splash u-boot u-boot_env rootfs all quit; do<br />
if [ "$howto" == "kernel" -o "$howto" == "all" ] ; then<br />
${DFU} -d ${HEX} -a kernel -R -U ${BACKUP_DIR}/kernel-${DATE}.bin<br />
fi<br />
if [ "$howto" == "splash" -o "$howto" == "all" ] ; then<br />
${DFU} -d ${HEX} -a splash -R -U ${BACKUP_DIR}/splash-${DATE}.bin<br />
fi<br />
if [ "$howto" == "u-boot" -o "$howto" == "all" ] ; then<br />
${DFU} -d ${HEX} -a u-boot -R -U ${BACKUP_DIR}/u-boot-${DATE}.bin<br />
fi<br />
if [ "$howto" == "u-boot_env" -o "$howto" == "all" ] ; then<br />
${DFU} -d ${HEX} -a u-boot_env -R -U ${BACKUP_DIR}/u-boot_env-${DATE}.bin<br />
fi<br />
if [ "$howto" == "rootfs" -o "$howto" == "all" ] ; then<br />
${DFU} -d ${HEX} -a rootfs -R -U ${BACKUP_DIR}/rootfs-${DATE}.jffs2<br />
fi<br />
if [ "$howto" == "quit" ] ; then<br />
exit 0<br />
fi<br />
echo<br />
echo 'the component(s) has/have been backed up, what next? (press enter for menu)'<br />
echo<br />
done<br />
<br />
exit 0<br />
<br />
</pre><br />
[[category:Guides]]<br />
[[category:Technical]]</div>DolfjeBot1http://openmoko.org/wiki/OrreryOrrery2008-08-31T12:55:20Z<p>DolfjeBot1: Replacing 'Freerunner' with 'FreeRunner'</p>
<hr />
<div>{{Application|Orrery}}<br />
<br />
== Overview ==<br />
The orrery is a simple open-source application for the Openmoko platform<br />
which displays the night (and day!) sky. It is nowhere near as elaborate as, for<br />
example Google Sky or xephem. It is intended to be a small application<br />
that will have a storage footprint comparable to a ringtone, or one of<br />
the games bundled with the openmoko rootfs. It requires no network connection,<br />
but does use the GPS information, by querying gpsd. <br />
It will be converted to work with Gypsy once the dbus based software stack<br />
becomes available.<br />
<br />
The star database was extracted from the Hipparcos catalog. To ease the<br />
computational load, the coordinates are not precessed or nutated before<br />
being displayed. Orbital elements are used,<br />
rather than ephemerides, to calculate planet positions. Although<br />
this is less accurate, it drastically reduces the memory<br />
footprint. The planet positions are accurate to a few arc<br />
minutes, from 3000 BC to 3000 AD. Since the scale<br />
on the default display is approximately 8 arc minutes<br />
per pixel, these small errors are imperceptible.<br />
<br />
== The Display ==<br />
<br />
[[Image:OrreryWithMenuTabs.png|Orrery with Menu Tabs]]<br />
<br />
The image above shows the default display - all stars visible to the unaided<br />
eye, with colors for the brightest ones. It's displayed with a <br />
Transverse Mercator projection (similar to Norton's Star Atlas) which works<br />
well with the VGA aspect ratio in portrait mode. <br />
It's a conformal transformation, so the<br />
constellations have about the right shapes. The Sun, Moon and planets are<br />
plotted, and the Moon is shown with the proper phase. The Sun and Moon are<br />
plotted with a size about 3.5 times larger than their true angular size on<br />
the sky.<br />
<br />
=== The orrery as a compass ===<br />
The green numbers at the bottom are the azimuth values. The<br />
azimuth is measured along the horizon, from north through east.<br />
So the azimuth of due north is 0, east is 90, south is 180<br />
and west is 270 degrees. By using these azimuth values, the<br />
orrery can be used as a celestial compass, if the sky above you<br />
is at least partially clear. Notice that the azimuth values are<br />
not exactly evenly spaced. This is caused by the distortion<br />
introduced by the Transverse Mercator projection.<br />
<br />
=== Constellations Display ===<br />
There are two display screens defined. By default, one of them shows<br />
the display shown above, and the other shows the constellations, and<br />
symbolic representations of the solar system objects.<br />
<br />
[[Image:OrreryFullScreenConstellations.png|Orrery Full Screen Constellation]]<br />
<br />
In addition to constellation names and figures, the Celestial Equator <br />
(light yellow), Ecliptic (red) and Galactic Plane (blue-green) are shown. <br />
Solar system objects are shown symbolically (see Mars, the Moon and the Sun<br />
in the above image).<br />
<br />
== Control Modes ==<br />
The orrery has two control modes, "finger mode" and "stylus mode".<br />
By default the program is in finger mode. In finger mode, the image <br />
can be panned by tapping your finger in<br />
the bottom 1/5 of the display (excluding menus). The size of<br />
the panning step is controlled by how close your finger is<br />
to the edge of the display. If you tap in the center, it pans<br />
by 0 degrees, and nothing happens. If you tap near the <br />
left or right edges, it<br />
pans by the maximum allowed amount, +-45 degrees. Pan steps are<br />
quantized in increments of 5 degrees. You may exit fullscreen mode<br />
by tapping anywhere in the upper 1/5 of the display area.<br />
Tapping anywhere else toggles between the two screens.<br />
<br />
If you are in stylus mode, the view can be panned around the sky by <br />
tapping the green arrows at the bottom, or the green azimuth values.<br />
In stylus mode, to exit from fullscreen you must tap in the area<br />
above the upper blue line, in the region where the time and location<br />
are displayed. Tapping anywhere else toggles between the two screens.<br />
<br />
There is a check box in the display menu which allows you to turn finger mode on and off.<br />
<br />
One may enter fullscreen mode by tapping the fullscreen button at the<br />
bottom left of the display.<br />
<br />
== Menus ==<br />
When not in fullscreen mode, three menus are displayed at the bottom of<br />
the screen.<br />
<br />
===Time===<br />
The time menu allows you to specify an<br />
explicit time between 3000 BC and 3000 AD, or the current<br />
time. If current time is selected, the display updates<br />
automatically once per minute. If a specific time is selected,<br />
it is shown in red, to remind you that the display is not<br />
going to update automatically as time passes.<br />
<br />
=== Place ===<br />
The place menu allows you to select the GPS-derived location,<br />
a user specified latitude and longitude, or a city or<br />
astronomical observatory selected from a menu. The lists of<br />
locations are stored in ASCII text files under the menus subdirectory<br />
of the program installation area on your phone. You may<br />
save your selected location, by hitting the "Save<br />
to Configuration File" button, so it will be used the<br />
next time you start the orrery. If you would like<br />
to add additional cities etc to one of the menus, you may simply<br />
edit one of the menu files, and add the name, latitude and longitude<br />
of the location. You will need to restart the orrery program for<br />
your new locations to become available.<br />
<br />
=== Display ===<br />
The display menu allows you to configure the display, selecting<br />
such things as the faintest magnitude object displayed, whether constellation<br />
lines are plotted, whether or not star names are displayed, etc.<br />
<br />
== Symbols ==<br />
=== Planet Symbols ===<br />
The solar system symbols, used by default on the constellation<br />
page (screen two), are the standard astronomical symbols for these<br />
objects. They are explained here:<br />
[http://en.wikipedia.org/wiki/Planet_symbols]<br />
<br />
=== Plotted Lines ===<br />
The dotted yellow line is the Celestial Equator, the intersection of<br />
the Earth's equatorial plane with the celestial sphere. The red<br />
dotted line is the Ecliptic. The Ecliptic is the intersection<br />
of the Earth's orbital plane with the celestial sphere. The<br />
Ecliptic is also the path of the Sun across the sky, and the intersection<br />
points between the Celestial Equator and the Ecliptic are where the<br />
Sun is at the time of an equinox. Constellations lying along the<br />
Ecliptic plane are zodiac constellations. The planets and the Moon <br />
are always near, but usually not exactly on, the Ecliptic.<br />
The blue-green dotted line is<br />
the Galactic Plane, the intersection of the plane of the Milky Way's<br />
disk and the celestial sphere.<br />
<br />
== System Requirements ==<br />
=== Supported Phones ===<br />
This program will run on either the neo1973 (gta01)<br />
or the FreeRunner (gta02). Users of the neo1973<br />
may wish to move the files to the microSD card, to<br />
save space in the limited builtin flash memory<br />
(see below).<br />
<br />
=== Supported Software Stacks ===<br />
This program has been tested running atop the<br />
2007.2 and 2008.8 distributions. It probably will<br />
work with FSO too. It is gtk based.<br />
<br />
=== Memory Requirements === <br />
This program requires 630 kbytes of storage space in the phone's<br />
builtin flash storage or microSD card. By default, most of<br />
the files (everything except the .desktop file, the launch<br />
icon and the executable) are stored under /usr/share/orrery.<br />
This directory tree may be moved elsewhere, if the new<br />
location is specified with the -d switch on the orrery<br />
invocation line in the .desktop file. The .desktop<br />
file resides in /usr/share/applications .<br />
<br />
== Installing this Program ==<br />
.ipk files for this program are now available for both the 2007.2<br />
and 2008.8 stacks, at the gForge site. It is much easier to install<br />
than it used to be. The program has been added to the community<br />
repository, so if you are running the 2008.8 stack, you need only<br />
type:<br />
<br />
'''opkg install orrery'''<br />
<br />
If you are running the 2007.2 stack, it is better (you get<br />
a better launch icon) if you download and install via<br />
opkg the latest .ipk file with 2007.2 in its name from here:<br />
[http://projects.openmoko.org/projects/orrery/].<br />
<br />
== Known Bugs ==<br />
=== Slow Display of Constellations ===<br />
The first time you tap the display<br />
to go into constellation mode, it takes several<br />
seconds to show the constellations. This only<br />
happens the first time - subsequent switches<br />
are pretty fast (< 1 second).<br />
<br />
=== Blurry Orion Label ===<br />
Ooops - I didn't remove some emacs backup files from<br />
my first .ipk files. The only visible<br />
effect of this that the name of the constellation<br />
Orion will be typed twice, slightly displaced from each<br />
other, one with a tilda (~) following it. You can fix<br />
that by removing the file<br />
/usr/share/orrery/constellations/Orion~ . This problem<br />
was fixed on the 1.1.1 .ipk file for 2007.2, and the<br />
1.1.2 .ipk file for 2008.8 .<br />
<br />
=== Restarting gpsd crashes orrery ===<br />
If you restart gpsd while the orrery is running, the<br />
orrery will crash if it is configured to use the GPS position.<br />
<br />
'''Send more bug reports!'''<br />
<br />
== Revision(ist) History ==<br />
Version 1.1 Changes:<br />
New user features:<br />
1) Added "finger mode", which allows<br />
orrery to be used without a stylus.<br />
This is now the default mode.<br />
2) Users can now specify which<br />
directory is the top of the data file <br />
tree for orrery. By default, this is <br />
/media/card/orrery, but the -d switch<br />
overrides this, so<br />
"orrery -d /usr/share/orrery"<br />
will tell orrery to<br />
look in /usr/share/orrery for the<br />
data files.<br />
3) The orrery will now display the names<br />
of some of the most prominent<br />
stars. This is not enabled by<br />
default, however - you must select<br />
this feature using the "display" menu.<br />
Bug Fixes:<br />
1) Fixed bug which caused cardinal point <br />
label ("North" etc) to be<br />
displayed at the top of the window <br />
rather than at the bottom, where<br />
it belongs.<br />
<br />
== Contact Information ==<br />
Please send comments, suggestions, questions and/or<br />
abuse to orrery.moko@gmail.com<br />
<br />
[[category:Applications]]<br />
[[category:GPS Applications]]</div>DolfjeBot1http://openmoko.org/wiki/Openmoko_Wiki_Official_Index_PageOpenmoko Wiki Official Index Page2008-08-31T12:54:30Z<p>DolfjeBot1: Replacing 'Freerunner' with 'FreeRunner'</p>
<hr />
<div>__NOTOC__<br />
<br />
{{todo|Add these articles into corresponding categories, in order to replace this page, with a dynamic category-based one}}<br />
<br />
==Introduction Of Openmoko==<br />
{| class="wikitable" cellspacing="1" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #eeeeee; background:#ffffff; width:100%;"<br />
|-<br />
! style="background:#ffffff;border-left:1px solid #ffffff;border-right:1px ; border-top:2px solid 75d806; border:1px solid #ffffff; width:50% " | <br />
<div align=left><br />
*[[Introduction]]<br />
*[[OpenmokoFramework]]<br />
*[[OpenmokoFramework/mickeyterm]]<br />
*[[Roadmap|Openmoko Roadmap]]<br />
*[[Meet_the_Core_Team|CoreTeam]]<br />
*[[Current events]]<br />
*[[Business Development]]<br />
</div><br />
! style="background:#ffffff;border-left:1px solid #ffffff;border-right:1px ; border-top:2px solid 75d806; border:1px solid #ffffff; width:50% " | <br />
<div align=left><br />
*[[Trademark Policy]]<br />
*[[License]]<br />
*[[Development_resources|Development Resources]]<br />
*[[WhyOpenmoko]]<br />
*[[DailyBuiltImages]]<br />
|}<br />
<br />
==Hardware ==<br />
{{Hardware}}<br />
===GTA01===<br />
{| class="wikitable" cellspacing="1" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #eeeeee; background:#ffffff; width:100%;"<br />
|-<br />
! style="background:#ffffff;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #ffffff; width:50% " align=left |<br />
*[[Neo1973]]<br />
*[[Neo1973 hardware]]<br />
*[[Disassembling Neo1973]]<br />
*[[Neo1973 Phase 1]]<br />
*[[Getting Started with your Neo1973]]<br />
===Hardware component===<br />
=====Audio=====<br />
*[[Neo1973 audio subsystem]]<br />
*[[LM4857]]<br />
=====Battery=====<br />
*[[Neo1973 Battery]]<br />
*[[Hardware:Neo1973:Alternate Cases:Extra battery]]<br />
*[[Neo1973 Battery Charger]]<br />
=====Power=====<br />
*[[Neo1973 Power Button]]<br />
*[[Neo1973 GTA01 Power Management]]<br />
=====USB=====<br />
*[[Neo1973 USB host]]<br />
=====Debug Board=====<br />
*[[Neo1973 Debug Board v2]]<br />
*[[Neo1973 Debug Board v3]]<br />
=====Development Board=====<br />
*[[QT2410]]<br />
=====Accessory=====<br />
*[[Car phone holder for neo1973]]<br />
*[[Related Hardware]]<br />
<br />
! style="background:#ffffff;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #ffffff; width:50% " align=left |<br />
=====Neo1973:Alternate Cases=====<br />
*[[Hardware:Neo1973:Alternate Cases]]<br />
*[[Hardware:Neo1973:Alternate Cases:Digital gaming]]<br />
*[[Hardware:Neo1973:Alternate Cases:Analogue gaming]]<br />
*[[Hardware:Neo1973:Alternate Cases:Gaming docking station]]<br />
*[[Hardware:Neo1973:Alternate Cases:Ruggedized]]<br />
*[[Hardware:Neo1973:Alternate Cases:Tamper-proof]]<br />
*[[Hardware:Neo1973:Alternate Cases:Square case]]<br />
*[[Hardware:Neo1973:Alternate CasesTrackstick]]<br />
*[[Hardware:Neo1973:Alternate Cases:Removal of free space]]<br />
*[[Hardware:Neo1973:Alternate Cases:Scroll-wheel (side-mounted)]]<br />
*[[Hardware:Neo1973:Alternate Cases:Alternate colours/materials]]<br />
*[[Hardware:Neo1973:Alternate Cases:Ambient light sensor]]<br />
*[[Hardware:Neo1973:Alternate Cases:Expansion Module Casing]]<br />
*[[Hardware:Neo1973:Alternate Cases:Touch strip sensor (side-mounted)]]<br />
*[[Hardware:Neo1973:Alternate Cases:Different speaker orientation]]<br />
*[[Hardware:Neo1973:Alternate Cases:General-purpose buttons (side-mounted) ]]<br />
*[[Hardware:Neo1973:Alternate Cases:Dual SIM ]]<br />
*[[Neo1973 as car gadget]]<br />
*[[Neo1973 as radio replacement]]<br />
|}<br />
===FreeRunner===<br />
{| class="wikitable" cellspacing="1" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #eeeeee; background:#ffffff; width:100%;"<br />
|-<br />
! style="background:#ffffff;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #ffffff; width:50% " align=left |<br />
<br />
*[[GTA02 Openness]]<br />
*[[Neo FreeRunner]]<br />
*[[Neo FreeRunner GTA02 Hardware]]<br />
*[[FreeRunner/Buttons and LEDs]]<br />
*[[Prototypes]]<br />
*[[GTA02 WLAN]]<br />
<br />
! style="background:#ffffff;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #ffffff; width:50% " align=left |<br />
<br />
===Openmoko Custom Build===<br />
*[[Openmoko-supported hardware]]<br />
*[[HXD8]]<br />
*[[Neo1973: GTA01Bv4 versus GTA02 comparison]]<br />
|}<br />
<br />
==Software==<br />
{| class="wikitable" cellspacing="1" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #eeeeee; background:#ffffff; width:100%;"<br />
|-<br />
! style="background:#ffffff;border-left:1px solid #ffffff;border-right:1px ; border-top:2px solid 75d806; border:1px solid #ffffff; width:50%" align=left | <br />
<br />
===U-boot===<br />
*[[U-boot|Bootloader]]<br />
*[[Bootloader_commands|Bootloader Command]]<br />
*[[Bootloader_environment|Bootloader Environment]]<br />
*[http://www.denx.de/wiki/UBoot u-boot]<br />
*[[Bootloader versions]]<br />
*[[NetBSD]]<br />
*[[Neo1973:GTA01:Kernel]]<br />
<br />
! style="background:#ffffff;border-left:1px solid #ffffff;border-right:1px ; border-top:2px solid 75d806; border:1px solid #ffffff; width:50%" align=left | <br />
<br />
===Linux Core Service===<br />
* [[Gsmd]]<br />
*[[Alarm daemon]]<br />
*[[Qpegps]]<br />
*[[D-Bus]]<br />
*[[Dbus device API]]<br />
*[[Opkg]]<br />
*[[QEMU command line]]<br />
<br />
|}<br />
==Application==<br />
{| class="wikitable" cellspacing="1" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #eeeeee; background:#ffffff; width:100%;"<br />
|-<br />
! style="background:#ffffff;border-left:1px solid #ffffff;border-right:1px ; border-top:2px solid 75d806; border:1px solid #ffffff; width:50% " align=left | <br />
<br />
===Application development tool===<br />
<br><br />
* [[Toolchain]]<br />
*[[OpenEmbedded]]<br />
*[[Java]]<br />
*[[Development with Eclipse]]<br />
*[[Dfu-util]]<br />
*[[Mono]]<br />
*[[PyFeedRead]]<br />
*[[Pexpect]]<br />
*[[Python]]<br />
*[[OpenOCD]]<br />
*[[SMSTool]]<br />
*[[BitBake]]<br />
*[[PulseAudio]]<br />
*[[Openmoko-debugtool]]<br />
*[[Libopkg]]<br />
===Openmoko Application Guideline===<br />
<br><br />
*[[Openmoko Community Applications]]<br />
*[[Openmoko Core Applications]]<br />
*[[Applications]]<br />
*[[Package management]]<br />
*[[Customizing the Openmoko Distribution]]<br />
*[[System Developer]]<br />
*[[Development Environment]]<br />
*[[Latest Images]]<br />
*[[Repositories]]<br />
*[[FreeRunner Software Status]]<br />
====Application Guideline====<br />
<br><br />
*[[Minimo|Building Minimo web browser ]]<br />
*[[Devirginator]]<br />
*[[File transfer]]<br />
*[[Getting GPS console output with gllin]]<br />
*[[Getting Started with your Neo FreeRunner]]<br />
! style="background:#ffffff;border-left:1px solid #ffffff;border-right:1px ; border-top:2px solid 75d806; border:1px solid #ffffff; width:50% " align=left | <br />
====Om2008.2====<br />
* [[Splinter|Splinter-GPS Application]]<br />
* [[Navit|Navit -GPS Application]]<br />
* [[Lint-wifi|Lint-Wifi:Wifi Networking tool]]<br />
* [[Mofi|Mofi:Networking tool]]<br />
* [[HP48 Series RPN Calculator]]<br />
* [[Tichy]]<br />
=====Om2007.2=====<br />
* [[Gutenflash]]<br />
* [[Calendar]]<br />
* [[Contacts]]<br />
* [[Music Player]]<br />
* [[Epdfview]]<br />
* [[Feed Reader]]<br />
* [[Dialer/2007.2]]<br />
* [[Messages]]<br />
* [[GPS Navigation]]<br />
* [[IM]]<br />
* [[Minimo]]<br />
* [[PyPenNotes]]<br />
* [[Search]]<br />
* [[Clock]]<br />
* [[Mokostat]]<br />
* [[Sample Native-Finger Application]]<br />
* [[Screen Grabber]]<br />
* [[Sketchbook]]<br />
* [[Frma71]]<br />
* [[Backup]]<br />
* [[Help Viewer]]<br />
* [[IM Presence]]<br />
* [[Media Player]]<br />
* [[MokoFEM]]<br />
* [[Mokopedia]]<br />
* [[Gutenflash]]<br />
* [[Orrery]]<br />
* [[Picture Viewer]]<br />
* [[Openmoko SMS Middleware]]<br />
* [[Zedlock]]<br />
<br />
|}<br />
{| class="wikitable" cellspacing="1" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #eeeeee; background:#ffffff; width:100%;"<br />
|-<br />
! style="background:#ffffff;border-left:1px solid #ffffff;border-right:1px ; border-top:2px solid 75d806; border:1px solid #ffffff; width:50% " align=left | <br />
====[[Distributions]]====<br />
* [[Qtopia on FreeRunner]]<br />
=====Om 2008.8=====<br />
*[[ASU Feature Plan]]<br />
*[[Userspace root image]]<br />
*[[Om2008.8 Locations]]<br />
*[[Om2008.8]]<br />
*[[Om2008.8 Installer]]<br />
*[[Om2008.8 Keyboard]]<br />
! style="background:#ffffff;border-left:1px solid #ffffff;border-right:1px ; border-top:2px solid 75d806; border:1px solid #ffffff; width:50% " align=left | <br />
=====FSO=====<br />
* [[GPRS FSO]]<br />
* [[FSO ringtones]]<br />
* [[OpenmokoFramework|FSO info]]<br />
* [[Zhone]]<br />
* [[Building FSO|Build FSO]]<br />
* [[FSO_UI_Tutorial|UI explanation]]<br />
* [[GPRS FSO|GPRS]]<br />
* [[FSO ringtones|Ringtones]]<br />
|}<br />
<br />
<br />
===Bug Report===<br />
*[[Bug Report]]<br />
<br />
==UI Design==<br />
{| class="wikitable" cellspacing="1" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #eeeeee; background:#ffffff; width:100%;"<br />
|-<br />
! style="background:#ffffff;border-left:1px solid #ffffff;border-right:1px ; border-top:2px solid 75d806; border:1px solid #ffffff; width:50% " align=left | <br />
===User Interface Guide===<br />
*[[Application UI Design Recommendations]]<br />
*[[Common Interface]]<br />
*[[GUI Style Guidelines]]<br />
*[[Neo1973 case schematics]]<br />
*[[Artwork]]<br />
*[[Preferences]]<br />
* [[Widget Inheritance Graph]]<br />
! style="background:#ffffff;border-left:1px solid #ffffff;border-right:1px ; border-top:2px solid 75d806; border:1px solid #ffffff; width:50% " align=left |<br />
===Widget===<br />
*[[Input Method]]<br />
*[[Power management menu]]<br />
* [[Main Menu]]<br />
*[[Finger Scrolling]]<br />
*[[File Open Dialog]]<br />
*[[UI Improvements]]<br />
====FSO UI====<br />
*[[FSO UI Tutorial]]<br />
|}<br />
<br />
=Test=<br />
{| class="wikitable" cellspacing="1" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #eeeeee; background:#ffffff; width:100%;"<br />
|-<br />
! style="background:#ffffff;border-left:1px solid #ffffff;border-right:1px ; border-top:2px solid 75d806; border:1px solid #ffffff; width:50% " align=left | <br />
=== Hardware ===<br />
[[GSM 900 RF Test Cases]]<br><br />
<br />
[[DCS 1800 RF Test Cases]]<br><br />
<br />
[[PCS 1900 RF Test Cases]]<br><br />
<br />
[[GSM 850 RF Test Cases]]<br><br />
<br />
[[Acoustic Test Cases]]<br><br />
<br />
=== Software===<br />
=== Neo FreeRunner ===<br />
* [[U-Boot Test Cases]] <br />
* [[Dialer Test Cases]]<br />
* [[Contacts Test Cases]]<br />
* [[Messages Test Cases]] <br />
* [[Charging Test Cases]]<br />
<br />
! style="background:#ffffff;border-left:1px solid #ffffff;border-right:1px ; border-top:2px solid 75d806; border:1px solid #ffffff; width:50% " align=left| <br />
== ASU Test Cases ==<br />
* [http://people.openmoko.org/testing/software/Testcases/version3/ASU_Qtopia_Dialer_v3.xls Qtopia Dialer Test Cases]<br />
* [http://people.openmoko.org/testing/software/Testcases/version3/ASU_Qtopia_Messages_v3.xls Qtopia Messages Test Cases]<br />
* [http://people.openmoko.org/testing/software/Testcases/version3/ASU_Qtopia_Contacts_v3.xls Qtopia Contacts Test Cases]<br />
* [http://people.openmoko.org/testing/software/Testcases/version3/ASU_Qtopia_Mine_Hunt_v3.xls Qtopia Mine Hunt Test Cases]<br />
* [http://people.openmoko.org/testing/software/Testcases/version3/ASU_Assassin_Installer_v3.xls Assassin(Installer) Test Cases]<br />
[http://people.openmoko.org/testing/software/Testcases/version3/ASU_Exposure_DateTime_v3.xls Exposure(Date & Time) Test Cases]<br><br />
* [http://people.openmoko.org/testing/software/Testcases/version3/ASU_Diversity_Splinter_v3.xls Diversity(Splinter) Test Cases]<br />
* [http://people.openmoko.org/testing/software/Testcases/version3/ASU_Systemsoftware_Suspend&resume_v3.xls Systemsoftware(Suspend & Resume) Test Cases]<br><br />
* [http://people.openmoko.org/testing/software/Testcases/version3/ASU_Systemsoftware_Charging_v3.xls Systemsoftware(Charging) Test Cases]<br />
* [http://people.openmoko.org/testing/software/Testcases/version3/ASU_E%20illume_Launcher_v3.xls E illume(Launcher) Test Cases]<br><br />
<br />
===Emulation===<br />
*[[Getting Openmoko working on host with Xephyr]]<br />
*[[Test_Openmoko Emulation with chroot image]]<br />
|}<br />
==Technical==<br />
{| class="wikitable" cellspacing="1" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #EEEEEE; background:#ffffff; width:100%;"<br />
|-<br />
! style="background:#ffffff;border-left:1px solid #ffffff;border-right:1px ; border-top:2px solid 75d806; border:1px solid #ffffff; width:50% " align=left | <br />
==Protocol/Standard==<br />
*[[IPv4]]<br />
*[[GSM]]<br />
*[[GSM02.07]]<br />
*[[GSMPowerDownInitScript]]<br />
*[[Pppd]]<br />
*[[DECT]]<br />
*[[Bluetooth]]<br />
*[[GPS]]<br />
====Hardware Documentation====<br />
*[[Supported microSD cards]]<br />
*[[Neo FreeRunner Memory Mapping]]<br />
*[[Hardware:AT Commands]]<br />
*[[Connecting Neo1973 with Debug Board v2]]<br />
*[[Connecting GTA01Bv2 with Debug Board]]<br />
*[[Compulab EM-X270]]<br />
*[[Technical:Accelerometer Fundamentals]]<br />
*[[Accelerometer data retrieval]]<br />
*[[NAND bad blocks]]<br />
*[[Boot from sd card]]<br />
*[[Charging battery directly]]<br />
====Software Documentation====<br />
*[[Keyboard Debate]]<br />
*[[Games]]<br />
*[[Biking]]<br />
*[[Illume]]<br />
*[[Debian]]<br />
*[[GPS Data Logger]]<br />
*[[Setting Date and Time]]<br />
*[[Simyo pppd scripts]]<br />
*[[Vibrator]]<br />
*[[Voice-recording.state]]<br />
*[[Sshfs]]<br />
*[[USB Networking with openSUSE]]<br />
*[[Dfu-util-windows]]<br />
*[[SHR Development]]<br />
**[[Pre-Flash Backup]]<br />
*[[Howto Test Your GPS with agpsui]]<br />
*[[GPS Problems]]<br />
*[[Building Openmoko 2007.1 from scratch]]<br />
*[[Host OS Tips]]<br />
*[[Neo1973 and Windows]]<br />
*[[Technical:P2P Radio]]<br />
*[[Host-based development with Xoo and Xephyr ]]<br />
*[[Customizing the Openmoko Distribution]]<br />
*[[Running Openmoko on PC]]<br />
*[[Flashing openmoko]]<br />
*[[How to run Openmoko Apps on PC]]<br />
*[[SettingsGUI]]<br />
*[[Automatic emulation in Ubuntu]]<br />
*[[Boot sound]]<br />
! style="background:#ffffff;border-left:1px solid #ffffff;border-right:1px ; border-top:2px solid 75d806; border:1px solid #ffffff; width:50% " align=left| <br />
<br />
*[[Building Gadget USB Module]]<br />
*[[Forcing fast charge mode]]<br />
*[[CheckFastCharge-script]]<br />
*[[MacOS X]]<br />
*[[Neo1973 Debug Board v2/Unbricking]]<br />
*[[No Linux]]<br />
*[[Openmoko under QEMU on Gentoo]]<br />
*[[Open GSM Radio]]<br />
*[[Openstreetmap]]<br />
*[[Booting from NFS]]<br />
*[[USB CDC ACM]]<br />
*[[Exporting hardware]]<br />
*[[Flashing openmoko/Known good kernel flash U-Boot output]]<br />
*[[Gsmd/document]]<br />
*[[Installing Pyroute]]<br />
*[[Kernel-dev-status-done]]<br />
*[[Migration to bad block tolerant builds]]<br />
*[[Nand erase]]<br />
*[[OSvS]]<br />
*[[Other OSes]]<br />
*[[PIM Storage]]<br />
*[[Package management]]<br />
*[[Phoned]]<br />
*[[Ringtones]]<br />
*[[Manually using GSM]]<br />
*[[Manually using GPRS]]<br />
*[[Manually using Bluetooth]]<br />
*[[Manually using SMS]]<br />
*[[WiFi support in Openmoko]]<br />
*[[Development Branches Policy]]<br />
*[[Import Sim Contacts]]<br />
*[[VCard import]]<br />
*[[GPS Sight]]<br />
*[[Distributions]]<br />
*[[Available Packages]]<br />
*[[Switching Keyboards]]<br />
====Training Programs====<br />
*[[Regular Training Programs]]<br />
|}<br />
<br />
<br />
==Wish List==<br />
{| class="wikitable" cellspacing="1" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #eeeeee; background:#ffffff; width:100%;"<br />
|-<br />
! style="background:#ffffff;border-left:1px solid #ffffff;border-right:1px ; border-top:2px solid 75d806; border:1px solid #ffffff; width:50% " align=left| <br />
===Hardware Ideas===<br />
*[[Kuai Yi Dian GM519]]<br />
*[[Wishlist:Expansion Back]]<br />
*[[Wish List]]<br />
*[[Wishlist - Hardware - Novel Devices]]<br />
*[[Wishlist:Unlikely]]<br />
*[[Wishlist:Accessories]]<br />
*[[Wishlist:Expansion]]<br />
*[[Wishlist:Auto Align Map]]<br />
*[[Wishlist:LiveUSB distro]]<br />
*[[Hardware:NearlyTouchScreen]]<br />
*[[Modular phone]]<br />
*[[Digital Television]]<br />
===Calling Feature===<br />
*[[Wishlist:Least Cost Routing]]<br />
*[[Wishlist:Headset Emulator]]<br />
*[[Anti-Theft Mode]]<br />
<br />
! style="background:#ffffff;border-left:1px solid #ffffff;border-right:1px ; border-top:2px solid 75d806; border:1px solid #ffffff; width:50% " align=left|<br />
===Software Ideas===<br />
*[[Wishlist:Data Traffic Monitor]]<br />
*[[Wishlist:Extension Framework]]<br />
*[[Wishlist:NeoMidiTracker]]<br />
*[[Wishlist:NeoWhistle]]<br />
*[[Wishlist:Human screening]]<br />
*[[Wishlist:Silent mode timeout]]<br />
*[[Wishlist:Graphics Tablet]]<br />
*[[Student phone]]<br />
*[[Wishlist:3D Viewport]]<br />
*[[Answering Machine]]<br />
*[[Mebot]]<br />
*[[Proposal for context management]]<br />
*[[MiLF interface]]<br />
*[[Wishlist:Software:GPS proxy]]<br />
*[[Server:WebProxy]]<br />
<br />
|}<br />
<br />
==Community & Users==<br />
<br />
{| class="wikitable" cellspacing="1" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #eeeeee; background:#ffffff; width:100%;"<br />
|-<br />
! style="background:#ffffff;border-left:1px solid #ffffff;border-right:1px ; border-top:2px solid 75d806; border:1px solid #ffffff; width:50%" align=left| <br />
===Community===<br />
*[[CommunityRepository]]<br />
*[[Community Updates]]<br />
*[[Community Member of the Week]]<br />
*[[FreeRunner: Selected Blogs and Articles]]<br />
*[[Openmoko:Community_Portal|Community Portal]]<br />
===Openmoko Local Groups===<br />
*[[Openmoko Local Groups]]<br />
! style="background:#ffffff;border-left:1px solid #ffffff;border-right:1px ; border-top:2px solid 75d806; border:1px solid #ffffff; width:50% " align=left | <br />
===Wiki Editing===<br />
*[[Wiki maintain agenda]]<br />
*[[Wiki Maintainers]]<br />
*[[Openmoko Wiki Editing Guidelines]]<br />
===Forums===<br />
*[http://forums.makeopensource.com/ Unofficial Openmoko Forums]<br />
*[[Discussion Forums]]<br />
|}<br />
==Service==<br />
{| class="wikitable" cellspacing="1" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #EEEEEE; background:#ffffff; width:100%;"<br />
|-<br />
! style="background:#ffffff;border-left:1px solid #ffffff;border-right:1px ; border-top:2px solid 75d806; border:1px solid #ffffff; width:50% " align=left | <br />
*[[Carriers]]<br />
*[[Carriers/TMobile]]<br />
*[[Carriers/ATT]]<br />
*[[Carriers/Rogers]]<br />
*[[Interested in second hand neo]]<br />
*[[P1 Buying Interest List]]<br />
*[[Buying Interest List]]<br />
*[[P1 Owners]]<br />
*[[Shop:Speedevil]]<br />
===Shipment===<br />
*[[Shipping Notes]]<br />
*[[Where is my FreeRunner?]]<br />
! style="background:#ffffff;border-left:1px solid #ffffff;border-right:1px ; border-top:2px solid 75d806; border:1px solid #ffffff; width:50% " align=left| <br />
====GroupSales====<br />
*[[GroupSales]]<br />
*[[MadridGroupSale]]<br />
*[[IberiaGroupSale]]<br />
*[[GroupSales/Torino]]<br />
*[[Group Sales Australia]]<br />
===Provider===<br />
*[[Neo1973 compatible cellphone providers]]<br />
|}<br />
{| class="wikitable" cellspacing="1" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #eeeeee; background:#ffffff; width:100%;"<br />
|-<br />
! style="background:#ffffff;border-left:1px solid #ffffff;border-right:1px ; border-top:2px solid 75d806; border:1px solid #ffffff; width:50% " align=left | <br />
==FAQ==<br />
*[[FAQ]]<br />
*[[SH1 FAQ]]<br />
*[[Neo FreeRunner (GTA02) FAQ]]<br />
*[[Distribution Customization FAQ]]<br />
*[[Application Development FAQ]]<br />
<br />
==[[Policies]]==<br />
{| class="wikitable" cellspacing="1" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #eeeeee; background:#ffffff; width:100%;"<br />
|-<br />
! style="background:#ffffff;border-left:1px solid #ffffff;border-right:1px ; border-top:2px solid 75d806; border:1px solid #ffffff; width:50% " | <br />
<div align=left><br />
*[[Bug Filing Policy]]<br />
*[[Openembedded Merge Policy]]<br />
<br />
</div><br />
==Mailing List==<br />
*[http://lists.openmoko.org/mailman/listinfo/ Mailing List]<br />
<br />
==Help==<br />
*[[Explaining carriers versus phones]]<br />
*[[Openmoko Wiki Editing Guidelines]]<br />
*[[Openmoko Wiki Editing Guidelines/zh cn]]<br />
<br><br />
<br><br />
! style="background:#ffffff;border-left:1px solid #ffffff;border-right:1px ; border-top:2px solid 75d806; border:1px solid #ffffff; width:50% " align=left | <br />
==Events==<br />
*[[SFBayAreaGetStarted]]<br />
*[[Summer of Code 2008]]<br />
*[[Openmoko Education/zh tw]]<br />
*[[Events:FOSDEM 2008]]<br />
*[[Current events]]<br />
*[[Openmoko Education Interview]]<br />
*[[Openmoko OpenLab Opening]]<br />
*[[Openmoko Visits and Hiring Day/zh tw]]<br />
*[[ETel]]<br />
*[[Press Coverage]]<br />
<br />
===Information===<br />
*[[Getting Openmoko]]<br />
*[[ChangeLog]]<br />
*[[DailyBuiltImages]]<br />
*[[External links]]<br />
*[[Glossary]]<br />
*[[Geocaching]]<br />
*[[Personas]]<br />
<br />
|}<br />
<br />
[[Category:Neo FreeRunner Hardware]]<br />
[[Category:Information| ]]<br />
[[Category:Openmoko| ]]</div>DolfjeBot1http://openmoko.org/wiki/Openmoko_Wiki_Editing_GuidelinesOpenmoko Wiki Editing Guidelines2008-08-31T12:54:19Z<p>DolfjeBot1: Replacing 'Freerunner' with 'FreeRunner'</p>
<hr />
<div>Our Openmoko Wiki Editing Guidelines are meant to assist our users in editing this wiki. They try to ensure a somewhat more consistent and organized structure.<br />
<br />
<br />
== Naming ==<br />
<br />
# Openmoko refers only to the software (think Openmoko GNU/Linux distribution), not to any of the devices<br />
# Neo 1973 is the first hardware device that officially runs Openmoko, Neo FreeRunner is the second<br />
# Use "the smartphone" if you refer to a hardware device that could be Neo 1973 but could also be a later version<br />
<br />
== Rules ==<br />
<br />
# If you see an error, correct it!<br />
# If you see a page that is mis-categorized, correct it!<br />
# If you're adding information (especially pages) about the hardware, keep in mind that the Neo 1973 is only one of the various devices that will run Openmoko. Thus,<br />
## Do not create generic pages like "Battery", rather use "Neo 1973 Battery".<br />
## If it makes sense to have generic pages, use per-device sections and make sure you always link to the Neo 1973 section from other Neo 1973 specific pages.<br />
## See [[Openmoko_Wiki_Editing_Guidelines#Style Sheet|Style sheet]] section for a list of other definitive spellings used in the Openmoko project.<br />
# The wiki is primarily meant to contain factual information on actual project software, hardware, even though parts might still be under development. Thus,<br />
## If you're adding information about wishlist items (or even more imaginary things), please clearly mark them with a "Wishlist:" prefix in the page title.<br />
## Always make sure that an outside user can clearly distinguish between the actual feature set of the device, and "interesting theoretical plans of what one could do if he had time" :)<br />
# Avoid duplication! Multiple sources often get out of sync, leading to confusion and mis-information. If you have new information see if it is an appropriate addition to an existing page. If you do feel that a new page is in order, remove duplicated information from the existing page and consolidate in your new page.<br />
# Use categories! We are trying to use categories as a way to help newcomers find what they want. Proper categorization of your new page or any existing pages will help bring your valuable information to the eyes of the user, and will help raise the level of usefulness of the entire wiki<br />
<br />
== Adding a new page ==<br />
<br />
To start a new page you can either create a link to it first on another page, like this: <br />
<br />
<nowiki>[[My new page]]</nowiki><br />
<br />
then click the resulting link and start editing the new page, or you can add your new page name to the URL in your browser's address-bar, like this: <br />
<br />
<nowiki>http://wiki.openmoko.org/wiki/My_new_page</nowiki><br />
<br />
and create the page first, before linking to it, or allow the wiki nannies to do the linking for you... they will see your page show up here:<br />
<br />
http://wiki.openmoko.org/wiki/Special:Recentchanges<br />
<br />
== Use categories ==<br />
<br />
Adding [[Special:Categories | categories]] to a page allows the wiki engine to organize the content automagically. This allows readers to find information in an organized way.<br />
<br />
* Please add a category at the bottom of the pages you create, trying to select the one most-accurate category for the page. <br />
* If a page truly fits in multiple categories, OK, but the wiki will be more organized if you pick the one most-accurate category.<br />
* Review the existing category hierarchy on the [[:Category:Categories]] page. (Be sure to press the + buttons to see the subcategories.)<br />
* A complete flat list of categories is available on the special [[Special:Categories|categories]] page.<br />
* If a category does not exist and you think a new one is required then use the same category syntax to create a new one.<br />
<br />
To add your page to a category:<br />
<br />
<pre><br />
[[Category:My selected category]]<br />
[[Category:My new category]]<br />
</pre><br />
<br />
If you are creating a new category, then be sure to click on the new category link and define what you were thinking should go into this category. Please be brief so readers will easily see the automatically indexed page links below your introduction text.<br />
<br />
To link to a category page within the page text:<br />
<pre><br />
[[:Category:My new category | My new category]]<br />
</pre><br />
<br />
For more help on categories, please see [http://www.mediawiki.org/wiki/Help:Categories MediaWiki's "Categories" help page.]<br />
<br />
== Use templates ==<br />
<br />
Please see available [[Templates]] and add them where necessary.<br />
<br />
=== Navigation templates ===<br />
<br />
Exemples: [[Template:Om_2008.8]], [[Template:OM2007.2]]<br />
<br />
These are most useful to present small sets of chronological or otherwise <br />
well ordered information items. For example, it's obvious to offer navigation <br />
templates between these articles:<br />
* Openmoko produced smartphones {GTA01 Neo 1973, GTA02 Neo FreeRunner, GTA 03 <br />
(speculative)}<br />
* Distributions {2007.1, 2007.2, 2008.8 ASU, 2008.9, FSO, SHR, Qtopia, Debian}<br />
<br />
In effect navigation templates create a subset of important pages presented sequentially. This corresponds more or less to a chapter in the user manual. We should not force them where they cannot create a CONSISTENT forth-and-back navigation between a GROUP OF PAGES.<br />
<br />
See also: http://en.wikipedia.org/wiki/Wikipedia:Navigation_templates<br />
<br />
== List pages ==<br />
<br />
List pages are manually maintained pages, which link to a certain set of articles. Their purpose is similar to category pages' automatic article listing, but they can provide advantages above the automatic lists, like sections, better formatting, sorting.<br />
<br />
An index page is only justified if it gives value added to the reader by<br />
* Making a thematic selection of quality links within and/or outside the Wiki<br />
* Providing a well thought out logical organization that makes it easy to find information<br />
* Offering a good formatting consistent with the above goal Indexes should be not be painful to maintain. Comprehensive lists of pages cannot be kept up to date and are better made automatically using categories.<br />
<br />
You are welcome to create and improve list pages which match these recommendations.<br />
<br />
See also: http://en.wikipedia.org/wiki/Wikipedia:Categories,_lists,_and_navigation_templates<br />
<br />
== Style Sheet ==<br />
=== A list of definitive spellings used throughout the site ===<br />
<br />
* Numbers [0-9]<br />
** 1973 <br />
***(the model name of the first Openmoko phone)<br />
*A<br />
<br />
*B<br />
<br />
*C<br />
<br />
*D<br />
<br />
*E<br />
<br />
*F<br />
** FreeRunner <br />
***(not freerunner or FreeRunner)<br />
***(the model name of the 2nd Openmoko phone, technically GTA02)<br />
*G<br />
<br />
*H<br />
<br />
*I<br />
<br />
*J<br />
<br />
*K<br />
<br />
*L<br />
<br />
*M<br />
** MokoMakefile (and it's '''not''' a script)<br />
<br />
*N<br />
** Neo<br />
*** (the brand name of Openmoko phones)<br />
** Neo 1973<br />
*** (the brand and model name of the first Openmoko phone)<br />
*** (not neo1973 or neo 1973. Note this has changed during the course of the project and a lot of current entries in the Wiki and software are wrong. See [http://lists.openmoko.org/pipermail/community/2008-February/013136.html here] for the official pronouncement as of February 2008)<br />
** Neo FreeRunner <br />
*** (the brand and model name of the second Openmoko phone)<br />
*** (not NeoFreeRunner or neo freerunner)<br />
<br />
*O<br />
** "Openmoko" or "Om"<br />
*** (the name of the complete software stack)<br />
*** (not "OpenMoko" anymore as of [http://www.businesswire.com/portal/site/home/?newsLang=en&viewID=news_view_popup&epi-content=NEWS_VIEW_POPUP_TYPE&beanStrID=reportcenterndm&newsId=20080304005158 March 2008].)<br />
** Openmoko Inc<br />
*** (the name of the Taiwanese company that develops products for the project)<br />
** openmoko.org<br />
*** (the community, non-commercial website for the project)<br />
** openmoko.com<br />
*** (the commercial website and webshop of Openmoko Inc)<br />
** Om 2007.2<br />
*** (the second version of the Openmoko distribution)<br />
** Om 2008.8<br />
*** (according to [[User:William Lai|William Lai]] [http://lists.openmoko.org/pipermail/documentation/2008-August/000275.html])(the third version of the distribution)<br />
*P<br />
<br />
*Q<br />
<br />
*R<br />
<br />
*S<br />
<br />
*T<br />
<br />
*U<br />
<br />
*V<br />
<br />
*W<br />
<br />
*X<br />
<br />
*Y<br />
<br />
*Z<br />
<br />
== Follow up on your own pages ==<br />
<br />
When you create a new page, it's a good idea to add it to your watchlist. Check your watchlist regularly to keep up with the evolution of the pages you have created, help the new editors of your page.<br />
<br />
== See also ==<br />
<br />
See also sections are for linking to other '''related articles in this Wiki'''. For external links please create an '''External links''' section instead. We encourage adding see also links to pages.<br />
<br />
* [[Edit Wiki]]<br />
* [[Wiki Issues]]<br />
<br />
<br />
{{Languages|Openmoko_Wiki_Editing_Guidelines}}<br />
<br />
[[Category:Wiki Editing]]</div>DolfjeBot1http://openmoko.org/wiki/Openmoko_Local_Groups:_VancouverOpenmoko Local Groups: Vancouver2008-08-31T12:54:00Z<p>DolfjeBot1: Replacing 'Freerunner' with 'FreeRunner'</p>
<hr />
<div>{|border=1<br />
!Name<br />
!Skills<br />
!Level of Interest<br />
!Location<br />
!Has Device<br />
!Has DebugBoard<br />
|-<br />
|mmontour<br />
|Developer<br />
|Hoping to organize an Openmoko presentation for [http://www.vanlug.bc.ca VanLUG] later this year.<br />
|Vancouver<br />
|[[Image: Moko.jpg|center]]<br />
|[[Image: MokoBox.jpg|center]]<br />
|-<br />
|[[User:romulus|rtymensen]]<br />
|development, pm<br />
|waiting for GTA02, porting apps<br />
|richmond<br />
|<br />
|<br />
|-<br />
|[[User:aufumy|aufumy]]<br />
|development<br />
|php, linux, opensource<br />
|Vancouver<br />
|[[Image: Moko.jpg|center]]<br />
|[[Image: MokoBox.jpg|center]]<br />
|-<br />
|[[User:alau42|alau42]]<br />
|user<br />
|Hope that my FreeRunner will actually function as a phone one day...<br />
|Vancouver<br />
|[[Image: Moko.jpg|center]]<br />
|[[Image: MokoBox.jpg|center]]<br />
|-<br />
|[[User:You|Your name here]]<br />
|Anything<br />
|Put your interests here<br />
|Littletown<br />
|<br />
|<br />
|}<br />
<br />
[[Category:Openmoko Local Groups]]</div>DolfjeBot1http://openmoko.org/wiki/Openmoko_Local_Groups:_TenerifeOpenmoko Local Groups: Tenerife2008-08-31T12:53:50Z<p>DolfjeBot1: Replacing 'Freerunner' with 'FreeRunner'</p>
<hr />
<div>== ¡Bienvenido a la página de Openmoko Tenerife! ==<br />
<br />
De momento somos 5 a la espera del FreeRunner vía [[IberiaGroupSale|IberiaGroupSale]]. Habemos 2 ingenieros informáticos, 2 electrónicos y 1 usuario avanzado, por tanto, creo que formamos un equipito interesante. Iremos apuntando por aquí la actividad que vayamos teniendo.<br />
<br />
Pedimos una placa de debug para tenerla por aquí, por si hace falta <strike>destrozar</strike> <strike>arreglar</strike> algo.<br />
<br />
Si todavia no tienes uno, animate y si tienes dudas, pregúntanos sin mosca. Somos todos de [http://www.gulic.org/ GULiC] así y la forma más fácil de localizarnos es en el webchat de la web de GULiC. Como casualmente somos todos de Tenerife, el grupo lo bauticé Tenerife, pero si tienes un Openmoko y eres de otra isla, sobre la marcha nos renombramos a grupo de [[Openmoko_Local_Groups:_Canarias|Canarias]].<br />
<br />
Estos somos nosotros:<br />
<br />
{|border=1<br />
!Nombre<br />
!Habilidades<br />
!Intereses<br />
|-<br />
|[[User:amd77|amd77]]<br />
|Electrónica y linuxerismo variado<br />
|Quiero darle un poco de rienda suelta a la imaginación y desarrollar algo que no exista, y en especial, divulgar esta nueva forma de ver el hardware a todo el mundo<br />
|-<br />
|}<br />
<br />
[[Category:Openmoko Local Groups]]</div>DolfjeBot1http://openmoko.org/wiki/Openmoko_Local_Groups:_MunichOpenmoko Local Groups: Munich2008-08-31T12:53:14Z<p>DolfjeBot1: Replacing 'Freerunner' with 'FreeRunner'</p>
<hr />
<div>[[Category:Openmoko Local Groups]]<br />
==Hilf mit, eine Münchner Openmoko UserGroup aufzubauen!==<br />
<br />
Interessenten können sich hier eintragen. Wenns Interesse gibt, dann treffen wir uns einfach mal wo in München oder Umgebung.<br />
<br />
==Gruppendetails==<br />
====Interessenten der Gruppe====<br />
{|border=1<br />
!Name<br />
!Skills<br />
!Level of Interest<br />
!Location<br />
!Other<br />
!Has Device<br />
!Has Debug Board<br />
|-<br />
|[[User:MaxMustermann|Max Mustermann]]<br />
|Beispiel spielen<br />
|OM Nutzen, Monkey island zocken<br />
|Musterstadt<br />
|<br />
|[[Image:Moko.jpg|center]] gta02v5<br />
|[[Image:MokoBox.jpg|center]]<br />
|-<br />
|[[Special:Emailuser/Whoever|Whoever]]<br />
|Semi-DAU<br />
|<br />
|München / Ingolstadt<br />
|<br />
|not yet<br />
|not yet<br />
|-<br />
|[[Special:Emailuser/Koebi|koebi]]<br />
|user<br />
|use OM<br />
|München<br />
|<br />
|not yet<br />
|no<br />
|-<br />
|[[Special:Emailuser/Beni|Beni]]<br />
|Linux, Programmierung (PHP/JS/HTML/etc, Perl, Bash, bisschen Java)<br />
|Hauptsächlich PIM + GPS, aber natürlich auch kleine Gadgets nutzen (zb Monkey Island/Siedler1 zocken). Vielleicht bisschen an der Software basteln.<br />
|Bad Tölz<br />
|<br />
|[[Image:Moko.jpg|center]] gta02v5<br />
|werde keines haben<br />
|-<br />
|[[Special:Emailuser/wof|wof]]<br />
|Linux und mehr<br />
|Telefon nutzen und rumspielen<br />
|100 km östlich von München<br />
|<br />
|keines bisher<br />
|vorerst keins<br />
|-<br />
|[[Special:Emailuser/Krause|Georg]]<br />
|Linux<br />
|Telefon nutzen; Least Cost Routing<br />
|Ebermannstadt (Bamberg/Bayreuth)<br />
|<br />
|keines bisher<br />
|vorerst keins<br />
|-<br />
|[[Special:Emailuser/Case|Case]]<br />
|sysadmin<br />
|OM nutzen, SW Entwicklung, rumspielen<br />
|München<br />
|<br />
|GTA02<br />
|vorerst keins<br />
|-<br />
|[[Special:Emailuser/x|x]]<br />
|<br />
|<br />
|München<br />
|<br />
|<br />
|<br />
|-<br />
|[[Special:Emailuser/ronny|ronny]]<br />
|bissl Linux<br />
|nutzen, gucken was geht<br />
|westlich von München<br />
|<br />
|keins<br />
|keins<br />
|-<br />
|[[Special:Emailuser/bsx|bsx]]<br />
|Linux, Java, C<br />
|nutzen, SW basteln<br />
|München<br />
|<br />
|keins<br />
|keins<br />
|-<br />
|[[Special:Emailuser/peter_b|peter_b]]<br />
|(embedded) Linux, C/C++ ...<br />
|endlich n telefon des macht was ich will :-)<br />
|München<br />
|<br />
|GTA02<br />
|keins<br />
|-<br />
|[[Special:Emailuser/swaesch|swaesch]]<br />
|Linux<br />
|use Openmoko<br />
|München / Ingolstadt<br />
|<br />
|GTA02<br />
|keins<br />
|-<br />
|[[Special:Emailuser/datenwolf|datenwolf]]<br />
|<br />
* Linux/Kernel<br />
* Echtzeit-Graphik<br />
* Low-Level-Programmierung<br />
* Netzwerk<br />
|<br />
* Rumbasteln<br />
* Neues Gehäuse entwerfen und bauen<br />
* am Display und den Eingabemöglichkeiten rum-modden (multitouch?)<br />
* eigenes Framework basteln (des Lernens wegen)<br />
* versuchen die Glamo-GPU voll auszureizen.<br />
* OpenGL-ES implementieren (entweder mit Glamo-GPU, oder in Software)<br />
* iPhone-artiges UI basteln<br />
|München/Moosach/Borstei<br />
|<br />
|GTA02v6<br />
|v3<br />
|-<br />
|[[User:Calestyo|Cálestyo Nótendil]]<br />
|Diplinf<br />
|<br />
* telefonieren :P<br />
* rumspielen<br />
* Leute ärgern, die ihr GTA02 noch nicht bekommen haben (Marcel?! ;) )<br />
|Candidplatz<br />
|<br />
|GTA02v5<br />
|noch nicht<br />
|-<br />
|[[Special:Emailuser/rema|rema]]<br />
|Linux User (seicht)<br />
|<br />
* telefonieren<br />
* GPS für Open Street Map (TangoGPS)<br />
* Musik hören<br />
|Ackermannbogen<br />
|<br />
|GTA02v5<br />
|nö<br />
|}<br />
<br />
====Stammtisch und sonstige Treffen====<br />
Es gibt derzeit leider noch keinen festen Stammtisch.<br />
*'''Ort:''' Keiner, Augustinerkeller, Arnulfstr. 52?<br />
*'''Zeit:''' Keine, 1x im Monat?<br />
<br />
<br />
=====GroupSale Treffen=====<br />
Das Treffen war am 7 Juli im Augustiner-Keller mit 8 Anwesenden ganz ordentlich besucht.<br />
<br />
* [[Special:Emailuser/Koebi|koebi]] organisiert den Kauf + Versand. Vielen Dank an dieser Stelle. Übergabe der Geräte persönlich in München and die die kommen können, der Rest wird versandt. (Portokosten sind noch zu klären, dann schlagen, die kommen noch zum Preis dazu.)<br />
<br />
* Koebi klärt, wo wir letztendlich kaufen und frägt hierzu bei den beiden in der Wikipage besprochenen Resellern nach Konditionen.<br />
<br />
* Philipp wollte versucht, zwecks UserGroup die Räume des CCC in München anzuzapfen. Bernd ist Mitglied im CCC und frägt mal nach.<br />
<br />
* Die Kommunikation soll möglichst zentral im Wiki laufen, damit auch externe was von der Gruppe mitbekommen.<br />
<br />
* Diskussionen sollten in Zukunft auch auf der [[Talk:Openmoko_Local_Groups:_Munich|Diskussionsseite]] stattfinden.<br />
<br />
== Sammelbestellungen ==<br />
<br />
[http://wiki.openmoko.org/wiki/GroupSales#M.C3.BCnchen GroupSales Seite]<br />
<br />
Der GroupSale wurde erledigt. Bestellt wurde bei Pulster, die Geräte sind mittlerweile da. Organisiert hat das ganze [[User:koebi|koebi]], vielen Dank nochmal an dieser Stelle!<br />
<br />
Zur Zeit ist kein weiterer Groupsale geplant; falls du interesse an einer Sammelbestellung hast, trag dich unter diesem Absatz ein!<br />
<br />
== GPS-Problem ==<br />
[[User:Beni|Beni]] 14:14, 16 July 2008 (UTC): Auf der Mailingliste tauchte die letzten Tage ein nicht unerheblicher Bug in Zusammenhang mit GPS/SD auf: der SD-Kartenleser hat aufgrund von Interferenzen offenbar Auswirkungen auf den GPS-Empfänger, der keinen FIX für Satelliten mehr bekommt, wenn eine SD-Karte eingelegt ist. Es ist bereits ein Kernelpatch in der Mache, der der SD-Karte den Saft abdreht, wenn sie nicht gebraucht wird; was allerdings das Problem nur teilweise entschärft. Desweiteren testen die Entwickler gerade einen HW-Fix. So, meine Frage ist jetzt die, ob der HW-Fix in unserer Lieferung bereits enthalten sein wird. GPS ist für mich schon ein recht wichtiges Feature! Was passiert, wenn der Fix nicht enthalten ist? Wird die Auslieferung seitens Pulster verzögert, damit der Fix noch mit reinkommt?<br />
koebi: ich werde bei pulster nachfragen.<br />
<br />
Für den HW-Fix des SD/GPS Problems muss ein SMD 10pF Kondensator eingelötet werden. Ich würde vorschlagen dass wir für einen SMD-Löt-Workshop einen Termin nach der Lieferung finden (also ab KW31) für ein Treffen in den µc³-Räumen in der Balanstr. (da gäb's jedenfalls Lötkolben und Kondensatoren)<br><br />
Geeignet (bzgl. Räume) wäre der Dienstag, die Frage ist nur ob die Neos bis dahin schon geliefert sein werden?<br><br />
--[[User:X|x]] 10:40, 18 July 2008 (UTC)<br />
<br />
Die Hardware Lösung sieht ziemlich einfach aus. Hätte auch das nötige Werkzeug ...<br />
<br />
[[Image:Gta02_gps_10pf_rework_sop.pdf]]<br />
<br />
--[[User:Datenwolf|Datenwolf]] 10:23, 31 August 2008 (UTC): Ich habe gestern endlich mein GTA02v6 erhalten. Beim Auspacken habe ich gleich die Lötstation vergewärmt und den 10pF-Kondensator bereitgelegt... Um dann festzustellen, dass beim v6 bereits ein 10pF eingelötet ist.<br />
<br />
--[[User:Peter b|Peter b]] 14:47, 18 July 2008 (UTC)<br />
<br />
[[User:Beni|Beni]] 13:21, 20 July 2008 (UTC) Cool, sieht wirklich nicht so schwer aus. Gott sei Dank :) Das mit der Verzögerung sollte sich damit verzögert haben, ich schätze stark, Pulster wird deswegen die Auslieferung nicht verzögern, weshalb wir uns alle auf kommende Woche freuen dürfen \o/<br />
Die Frage bleibt nur, ob unsere Garantie futsch ist, wenn wir das selber machen, oder ob Pulster vor der Übergabe an uns das vielleicht schon reinlötet... Koebi, kannst du das bitte checken?<br />
<br />
--[[User:Calestyo|Calestyo]] 20:41, 21 July 2008 (UTC): Hmm wenn Ihr Euch alle trefft um das zu reparieren,.. kann man da dann auch mitmachen, wenn man sein GTA02 schon hat (bestellt bei Pulster)? Wann genau wäre der Termin?<br />
<br />
:: koebi: ich denke das werden wir klar machen wenn wir unsere Lieferung bekommen haben, wird dann auch hier stehen.<br />
<br />
<br />
<br />
Was die Garantie angeht hab ich folgendes gefunden:<br />
[http://lists.openmoko.org/pipermail/community/2008-July/021638.html]<br />
[http://freeyourphone.de/portal_v1/viewtopic.php?f=13&t=251&p=2614#p2614]<br />
--[[User:Peter b|Peter b]] 08:20, 22 July 2008 (UTC)<br />
<br />
--[[User:ronny|ronny]] ich wollte nächste Woche sowieso eine Bestellung beim Reichelt machen. Würde da einfach mal 20x G0603 10P mitbestellen. Wenn ich das aus dem Text [[http://wiki.openmoko.org/wiki/GPS_Problems]] richtig rauslese ist zwar eigentlich 0402 nötig, aber das sollte man scho hinkriegen. Weiter hab ich in dem Text noch bezüglich Garantie das hier gefunden: "The rework is not suggested to end users without hardware soldering technique and equipment." Sagt ja eigentlich alles aus.<br />
: koebi: was ist denn der unterschied zwischen dem vorgeschlagenen und dem den du bestellen willst?<br />
<br />
--[[User:Koebi|koebi]] auf meine Anfrage sagt Christoph Pulster folgendes:<br />
<pre>I have no infos at the moment how OM will handle the problem,<br />
at the moment I propose to use the software fix only.<br />
<br />
The hardware fix is mentioned here:<br />
http://wiki.openmoko.org/wiki/FreeRunner_Hardware_Issues#GPS_Slow_TTFF<br />
Please dont try the tricky soldering of the capacitor at you own.<br />
I can not give warranty on wrong soldered units, please understand.<br />
<br />
As soon as Openmoko has made a decision about the GPS problem, I will<br />
let you know. Then we will see if a shipping back of the unit for<br />
warranty repair is necessary or not.<br />
</pre><br />
(scheint mir ne kopierte standard-Antwort zu sein, daher englisch)<br />
<br />
--[[User:Peter b|Peter b]] 07:21, 23 July 2008 (UTC)<br />
Der Unterschied zwischen 0402 und 0603 ist die Grösse: 1.0x0.5mm bzw. 1.6x0.8mm. Ich denk aber auch dass der 0603 reinpasst (evtl. wird die Höhe ein Problem). Sorgen das beim Einbau irgendwas kaputt geht was meiner Garantie schadet hab ich dank "hardware soldering technique and equipment" nicht :-)<br />
<br />
So wie's aussieht dürften bis Anfang nächster Woche wohl alle ihren Neo haben. D.h. wer daran Interesse hat kann am nächsten Dienstag, wohl so irgendwann ab 1900-2000 in den [http://muc.ccc.de/treffen.html.de µc³-Räumen] zum HW-Fixen oder gerne auch Usergruppieren vorbeischauen.<br><br />
--[[User:X|x]] 12:25, 24 July 2008 (UTC)<br />
<br />
Ähm zwecks dem Treffen nochmals,...<br />
* Habt ihr genügend von den empfohlenen Kondis? Wenn ja die 0402er oder die größeren? Wie viel kosten die? Oder muss man die selber mitbringen?<br />
* Wer würde das dann machen? Ich selber habe leider nicht wirklich große Erfahrung beim Löten und insbesondere ne unzureichende Feinmotorik ^^<br />
* Treffpunkt 1900?<br />
--[[User:Calestyo|Calestyo]] 15:28, 4 August 2008 (UTC)<br />
<br />
Gibts noch mal ein Löttreffen?<br />
Ich würd ggf. mitmachen, wenns sichs zeitlich einrichten lässt.<br />
Btw, was habt ihr so für First-Fix Zeiten? ich hab, wenns gut läuft den Fix meistens nach etwa 200 sekunden, was schon bissl lang ist... Allerdings fehlen ja sämtliche almanac-daten. Die sollen ja bald kommen, zumindest im FSO werden die bald auftauchen. Wenn der Fix ersmtal da ist, ist er sehr stabil und die Signalqualität fast immer gut.<br />
--[[User:Beni|Beni]] 19:26, 4 August 2008 (UTC)<br />
<br />
* @Calestyo: Das Treffen war schon letzte Woche, von dieser woche weiss ich nix...<br />
* Also mein Rekord (ohne Hardware-Fix) waren 49 Sekunden, allerdings was das hier auf dem Hügel im Luidpoldpark...also mir reicht das eigentlich, ich löt erstmal nix. Ich fänd ein weiteres Treffen nicht schlecht, zumal ich mich das letzte mal hauptsächlich mit Pidgin rumgeschlagen habe...:) Bei Interesse könnten wir uns mal über ein regelmäßiges Treffen unterhalten, vielleicht ne Mailingliste einrichten oder so, auf dem Wiki ist das doch immer ein bischen aufwändig. Was meint ihr?<br />
<br />
--[[User:Nosyjoe|Nosyjoe]] 20:20, 4 August 2008 (UTC)<br />
<br />
[http://en.wikipedia.org/wiki/D%27oh! D'oh!] :-/ ... gibt es evtl. nochmal so ein Treffen oder ne Gelegenheit wo man das von professioneller Hand durchführen lassen kann?<br />
--[[User:Calestyo|Calestyo]] 20:25, 4 August 2008 (UTC)<br />
<br />
Ja, das ganze machen zu lassen ist sicher auch nicht blöd. Kennt jemand einen Lötservice in München? Mir fehlt es leider total an Equippment... ich würde es auch selber machen, wenns nicht anders geht, aber wie gesagt, bräuchte ich Equippment und Material. --[[User:Beni|Beni]] 14:19, 5 August 2008 (UTC)<br />
<br />
Also die Kondensatoren von oben sollten im Laufe der Woche bei mir ankommen. Lötstation (digital, kleine Lötspitze) könnte ich auch mitbringen. Desweiteren mache ich grad ein Praktikum bei Siemens, da komme ich auch an eine SMD-Lötstation ran, so mit Mikroskop und so -die kann ich aber leider nicht mitbringen.<br />
Mailingliste ist ne gute Idee. Treffen einmal im Monat wäre auch interessant, könnte zum Beispiel grad Hilfe mit dem Toolchain gebrauchen (-; --[[User:Ronny|Ronny]] 16:18, 5 August 2008 (UTC)<br />
<br />
Haben wir eine mailinglist für die MUC Gruppe?<br />
Abgesehen davon würde ich mich dann da gerne gleich für anmelden,... also deine Löt-Dienste in Anspruch zu nehmen. Zumindest wenn Du auch wirklich qualifiziert dazu bist ;-) ... nimm das nicht persönlich, aber erst vor wenigen Minuten hab ich von einem auf der ML gelesen,... der sich sein Moko schon kaputt gelötet hat... (auch nach dem Entfernen des Kondis, geht SD nicht mehr :-/ )<br />
Wie viele Kondis hast Du bestellt und wo genau?<br />
--[[User:Calestyo|Calestyo]] 20:22, 5 August 2008 (UTC)<br />
<br />
Ich hab mal eine mailinglist eingerichtet:<br />
<br />
openmoko@lists.muc.ccc.de<br><br />
http://lists.muc.ccc.de/cgi-bin/mailman/listinfo/openmoko<br />
<br />
0402 10pF KerKos liegen in den µc³-Räumen rum, Lötkolben/Werkzeug gibt's da auch, und Leute die einem beim Löten helfen sind auch oft anwesend. Letztes mal hat sich ja keiner getraut, ich auch nicht, hab das auch noch nicht nachgeholt, hab das aber vor. :)<br><br />
Im Moment sind bei mir die issues "Schutzfolie" und "2.5mm->3.5mm Klinker 'mit vielen Ringen'" höherpriorisiert... ;)<br><br />
Dienstag Abend (so etwa ab 1900) ist da - äh - 'öffentlich offen', also da kann man einfach vorbeischauen, die Wahrscheinlichkeit dass da andere Openmoko-User und/oder Leute die SMD-Löt-Erfahrung haben und gern helfen anwesend sind halte ich eigentlich immer für sehr hoch...<br><br />
<br />
Das mit der Toolchain hab ich grad erst schonmal hingekriegt (und 'nen gsm0710muxd compiled)...<br />
<br />
--[[User:X|x]] 13:24, 6 August 2008 (UTC)<br />
<br />
Super danke. Ich schreib mal trotzdem nochmal hier rein, weil ja noch nicht viele auf der Liste sind. Irgendeine Qualifikation hab ich nicht -nur etwas Hobbyerfahrung - würde auch lieber das vorher einmal üben und das nicht unbedingt an fremden Eigentum. Wobei ich mit dem Löten bei meinem eigenen noch ein bischen abwarten wollte... Ich schau's mir mal an und entscheide dann, ob ich's mir OHNE Schwierigkeiten zutraue.<br><br />
Ich fand beim letzten Mal das Equipment in den µc³-Räumen jetzt nicht unbedingt so gut.<br><br />
Hab versucht von der Moko-Projektseite die Alarmclock zu kompilieren, hab aber massig Libraries gebraucht, die nicht kompilieren wollten und deren vorkompielerte Versionen nicht zum Armv4t gepasst haben. <br>--[[User:Ronny|Ronny]] 15:31, 6 August 2008 (UTC)<br />
<br />
<br />
Also ist das nächste Treffen am '''Dienstag, 12.08.2008''' in den Münchner CCC-Räumen geplant? --[[User:Beni|Beni]] 07:26, 7 August 2008 (UTC)<br />
<br />
<br />
Also ich persönlich habe geplant nächsten Dienstag dort zu sein. Über anderer Leute Planung kann ich nix sagen. :)<br><br />
Zum Thema Toolchain hab ich 'ne kurze Zusammenfassung an die ML geschickt...<br><br />
--[[User:X|x]] 16:42, 7 August 2008 (UTC)<br />
<br />
Ich werds leider nicht schaffen.... --[[User:Beni|Beni]] 07:22, 11 August 2008 (UTC)</div>DolfjeBot1http://openmoko.org/wiki/Openmoko_Local_Groups:_MontrealOpenmoko Local Groups: Montreal2008-08-31T12:53:04Z<p>DolfjeBot1: Replacing 'Freerunner' with 'FreeRunner'</p>
<hr />
<div>Welcome to the Montreal Openmoko Enthusiasts page!<br />
<br />
<pre><br />
Please update this page with any information about local Openmoko happenings that you might know about.<br />
</pre><br />
<br />
== Meetings ==<br />
The following are a list of past and present meetups and demos in and around Montreal.<br />
<br />
=== Future ===<br />
<br />
{|border=1<br />
!Date<br />
!Type<br />
!Host<br />
!Location<br />
!Remarks<br />
|-<br />
|2007-10-14<br />
|MeetUp<br />
|[[User:Eric|Eric Preston]]<br />
|Mile End, Montreal<br />
|I'm hosting regular, informal Openmoko sessions at my apartment in Mile End. I plan to have one at least every month. Goto http://eric.linuxmontreal.com/contact to send me an email asking for directions and to reserve your spot. There is room for about 6-8 people.<br />
|}<br />
<br />
=== Past ===<br />
<br />
{|border=1<br />
!Date<br />
!Type<br />
!Host<br />
!Location<br />
!Remarks<br />
|-<br />
|2007-09-09<br />
| Meetup<br />
|[[User:Eric|Eric Preston]]<br />
|Mile End, Montreal<br />
|A couple of people met up at Eric's place to check out his Neo1973 GTA01Bv4 kits.<br />
|}<br />
<br />
<br />
== People ==<br />
The following is a list of people interested in Openmoko from in and around Montreal.<br />
{|border=1<br />
!Name<br />
!Skills<br />
!Level of Interest<br />
!Location<br />
!Has Device<br />
!Has Debug Board<br />
!Other<br />
|-<br />
|[[User:Eric|Eric Preston]]<br />
|Freelance Developer<br />
|Owner, Neo1973 Advanced, Base<br />
|Montreal<br />
| [[Image: Moko.jpg|center]]<br />
|[[Image: MokoBox.jpg|center]]<br />
|Organizing meetups as discussed above.<br />
|-<br />
|[[User:Opampca|Richard Lussier]]<br />
|Community networking<br />
|Getting a free phone developped for ISF network<br />
|Montreal<br />
|<br />
|<br />
|Part of [http://www.ilesansfil.org/ Ile Sans Fil]<br />
|-<br />
|[[User:Skwid|Benjamin Crulli]]<br />
|Programming<br />
|Developing some apps related to wifi hotspots<br />
|Montreal<br />
|<br />
|<br />
|Part of [http://www.ilesansfil.org/ Ile Sans Fil]<br />
|-<br />
|[[User:Youlian|Youlian Troyanov]]<br />
|Programming<br />
|Developing apps<br />
|Montreal<br />
|<br />
|<br />
|Mobile c++/java developer<br />
|-<br />
|[[User:Avoine|Patrick Hétu]]<br />
|Programming<br />
|Developing apps<br />
|Montreal<br />
|<br />
|<br />
|C/Python developer<br />
|-<br />
|[[User:R-R|Alexandre Guédon]]<br />
|Freelance FOSS advocate<br />
|VoIP, Mesh, Security, ...<br />
|Montreal<br />
|<br />
|<br />
|Cultural/Technical/Political interests<br />
|-<br />
|[[User:VdeGrandpré|Vincent de Grandpré]]<br />
|Étudiant en génie logiciel, ÉTS (UQ) - DEC Tech. de l'informatique (420.01)<br />
|Propriétaire, Neo1973 GTA01v4, Atmel STK500<br />
|Montréal, Québec<br />
| [[Image: Moko.jpg|center]]<br />
|[[Image: MokoBox.jpg|center]]<br />
|Développeur Java, C et bidouilleur expérimenté (débutant en logiciels embarqués).<br />
|-<br />
|[[User:R-R|René Paradis]]<br />
|bioinformaticien<br />
|open languages and software design<br />
|Quebec city<br />
|[[Image: Moko.jpg|center]]<br />
|<br />
|[http://www.zapquebec.org/ zapquebec] volunteer, cultural/technical interests<br />
|-<br />
|[[User:Wjbaird|Warren Baird]]<br />
|Product Manager, Software Developer, Photographer<br />
|Owner, OM FreeRunner<br />
|Montreal<br />
|[[Image: Moko.jpg|center]]<br />
|<br />
|<br />
|-|}<br />
<br />
<br />
See [[Talk:Openmoko_Local_Groups:_Montreal|discussion]]<br />
<br />
[[Category:Openmoko Local Groups]]</div>DolfjeBot1http://openmoko.org/wiki/Openmoko_Local_Groups:_MelbourneOpenmoko Local Groups: Melbourne2008-08-31T12:52:54Z<p>DolfjeBot1: Replacing 'Freerunner' with 'FreeRunner'</p>
<hr />
<div>Welcome to the Melbourne Openmoko usergroup.<br />
<br />
{|border=1<br />
!Name<br />
!Skills<br />
!Level of Interest<br />
!Location<br />
!Other<br />
|-<br />
|[[User:KellyV|Kelly Vlahovic]]<br />
|Linux, C, PHP<br />
|User and developer<br />
|Hawthorn, Melbourne<br />
|<br />
|-<br />
|[[User:Mcsporran|Johnny McKenzie ]]<br />
| Linux, Networking<br />
| User <br />
| City, Melbourne<br />
|<br />
|-<br />
|[[User:Antisol|Dale Maggee ]]<br />
| Following HOWTOs<br />
| User <br />
| Scumsborough, Melbourne<br />
|<br />
|-<br />
|[[User:Sjors|Sjors Provoost]]<br />
| Linux, PHP/Ruby/Python, (My)SQL, geo stuff<br />
| User, bit of developing <br />
| Preston, Melbourne<br />
|<br />
|-<br />
|[[User:rwh86|Robert Hutton]]<br />
| Linux,C/PHP/Perl,SQL<br />
| FreeRunner user, aspiring developer<br />
| North Melbourne<br />
|<br />
|}<br />
<br />
[[Category:Openmoko Local Groups]]</div>DolfjeBot1http://openmoko.org/wiki/Openmoko_Local_Groups:_LondonOpenmoko Local Groups: London2008-08-31T12:52:44Z<p>DolfjeBot1: Replacing 'Freerunner' with 'FreeRunner'</p>
<hr />
<div>Welcome to Openmoko London!<br />
<br />
Beer and Neo anyone?<br />
<br />
{|border=1<br />
!Name (IRC nick)<br />
!Skills<br />
!Interest<br />
!Location<br />
!Device owned<br />
|-<br />
|[[User:jptmoore|John Moore]] (zedstar)<br />
|C/Scheme<br />
|Application development<br />
|Pinner<br />
|[[Image: Moko.jpg|center]]<br />
|-<br />
|Alex<br />
|Java,Perl,Python<br />
|User & developer<br />
|Hampshire<br />
|<br />
|-<br />
|[[User:Phlash|Phil Ashby]]<br />
|C/C++/Java /Embedded/Hardware<br />
|Kernel & Application development<br />
|Felixstowe<br />
|[[Image: Moko.jpg|center]]<br />
|-<br />
|John Cass<br />
|Java,C<br />
|User & developer<br />
|London<br />
|[[Image: Moko.jpg|center]]<br />
|-<br />
|[[User:TonyGarnockJones|Tony Garnock-Jones]] (tonyg)<br />
|C, assembly, Erlang, Scheme, ML, Haskell, Smalltalk, ...<br />
|User & developer<br />
|London<br />
|[[Image: Moko.jpg|center]]<br />
|-<br />
|[[User:ThomasWood|Thomas Wood/OpenedHand]]<br />
|C, GTK+ developer<br />
|User & developer<br />
|London<br />
|[[Image: Moko.jpg|center]] [[Image: MokoBox.jpg|center]] + GTA02 (FreeRunner Prototype)<br />
|-<br />
|[[User:Stephmw|Steph Meslin-Weber]]<br />
|Java (J2ME), C, User Experience, Interface prototyping<br />
|User, developer and general busybody<br />
|London<br />
|-<br />
|[[User:WebJames|James Olney]]<br />
|General experience<br />
|User<br />
|Oxford<br />
|Wanted FreeRunner perhaps get into a 10pack group]<br />
|-<br />
|[[User:chrestomanci|David Pottage]]<br />
|Perl, Java (J2se), C<br />
|User & developer<br />
|Reading<br />
|FreeRunner<br />
|-<br />
|[[User:vermoos|Michael Nandris]]<br />
|Python/Plone ethusiast, interest in DPA (1998)<br />
|User, developer<br />
|London, Camden<br />
|Wanted FreeRunner perhaps get into a 10pack group]<br />
|-<br />
|[[User:Weiss|Weiss]]<br />
|C, GTK+, ARM Assembly, Perl, TCL<br />
|User, developer<br />
|Cambridge<br />
|Wanted FreeRunner [perhaps get into a 10pack group]<br />
|-<br />
|[[User:TimW|TimW]]<br />
|C++<br />
|User, developer<br />
|Pinner<br />
|FreeRunner<br />
|-<br />
|[[User:Menno|Menno Smits]]<br />
|Python, C, GTK+<br />
|User, apps development <br />
|London<br />
|FreeRunner<br />
|-<br />
|[[User:David_Hicks|Dave]]<br />
|C, SSL/TLS, POSIX threading<br />
|User, apps development <br />
|London<br />
|FreeRunner<br />
|-<br />
|Tina<br />
|User, Sys Admin<br />
|User (can compile, maybe port)<br />
|Oxford<br />
|FreeRunner<br />
|-<br />
|[[User:gnublade|Andy Kilner]]<br />
|Python, C, GTK+<br />
|User, Developer <br />
|London<br />
|FreeRunner<br />
|-<br />
|[[User:Vortex|Vortex]]<br />
|C, toolchains, distributions<br />
| mesh networking, service discovery, wifi, bluetooth, scanning, gps<br />
|London<br />
|FreeRunner<br />
|-<br />
|}<br />
Key:<br />
[[Image: Moko.jpg]] = GTA01<br />
[[Image: MokoBox.jpg]] = Debug board<br />
<br />
See [[Talk:Openmoko_Local_Groups:_London|discussion]]<br />
<br />
[[Category:Openmoko Local Groups]]</div>DolfjeBot1http://openmoko.org/wiki/Openmoko_Local_Groups:_FinlandOpenmoko Local Groups: Finland2008-08-31T12:52:29Z<p>DolfjeBot1: Replacing 'Freerunner' with 'FreeRunner'</p>
<hr />
<div>Finnish main page: [[Main_Page/fi|suomenkielinen pääsivu]].<br />
<br />
Finnish translators: [[Translation#Finnish|Openmoko-ohjelmien suomentaminen]].<br><br />
<sup>suomennettuja ohjelmia: [http://tangogps.org/ TangoGPS 0.9.3], [http://docs.openmoko.org/trac/gitweb?p=om-locations.git;a=summary om-locations], perus-gtk/qt/gnome-tavarat jotka tulevat muualta kyseisiltä projekteilta, ...</sup><br />
<br />
IRC channel: '''''#openmoko-fi''''' @ irc.freenode.net <sup>([http://java.freenode.net/index.php?channel=openmoko-fi Java-IRC] & [http://embed.mibbit.com/?server=irc.freenode.net&channel=%23openmoko-fi&noServerNotices=true&noServerMotd=true&forcePrompt=true Ajax-IRC])</sup><br><br />
<br />
==== Subgroups ====<br />
* [[Openmoko Local Groups: Helsinki|Helsinki]]<br />
* [[Openmoko Local Groups: Your city/area|Your city/area]]<br />
<br />
==== See also ====<br />
* [[GroupSales#Finland|Group Purchases of Neo FreeRunner devices in Finland]]<br><sup>group purchases mostly done, but still it would be possible to buy 10-packs from pulster.de for 299€/phone</sup><br />
<br />
[[Category:Openmoko Local Groups]]</div>DolfjeBot1http://openmoko.org/wiki/Openmoko_Local_Groups:_Erlangen-NuernbergOpenmoko Local Groups: Erlangen-Nuernberg2008-08-31T12:52:19Z<p>DolfjeBot1: Replacing 'Freerunner' with 'FreeRunner'</p>
<hr />
<div>=== Possible Participants ===<br />
{|border=1<br />
!Name<br />
!Skills<br />
!Level of Interest<br />
!Location<br />
!Other<br />
!Has Device<br />
!Has Debug Board<br />
|-<br />
|[[User:andrenarchy|Andrenarchy]]<br />
|C/C++, GTK+, dbus<br />
|Coding, Testing<br />
|Erlangen<br />
|just received my mass-production FreeRunner on 10th of July :D<br />
|[[Image: Moko.jpg|center]]<br />
|<br />
|}<br />
<br />
[[Category:Openmoko Local Groups]]</div>DolfjeBot1http://openmoko.org/wiki/Openmoko_Local_Groups:_East_TexasOpenmoko Local Groups: East Texas2008-08-31T12:52:09Z<p>DolfjeBot1: Replacing 'Freerunner' with 'FreeRunner'</p>
<hr />
<div>This is the Local User Group page for Houston and the surrounding areas. Please leave your info here if you're interested in meeting.<br />
<br />
<br />
{|border=1<br />
!Name<br />
!Skills<br />
!Level of Interest<br />
!Location<br />
!Other<br />
|-<br />
|[[User:Dogalmity|dogalmity]]<br />
|C, Linux kernel, C++, Java, SQL <br />
|Gonna get me that there FreeRunner contraption<br />
|Houston<br />
|<br />
|}<br />
<br />
[[Category:Openmoko Local Groups]]</div>DolfjeBot1http://openmoko.org/wiki/Openmoko_Local_Groups:_East_MidlandsOpenmoko Local Groups: East Midlands2008-08-31T12:52:00Z<p>DolfjeBot1: Replacing 'Freerunner' with 'FreeRunner'</p>
<hr />
<div>Welcome to Openmoko East Midlands<br />
<br />
Anyone else here?<br />
<br />
{|border=1<br />
!Name<br />
!Skills<br />
!Interest<br />
!Location<br />
!Device owned<br />
|-<br />
|[[User:nick|nick]]<br />
|Basic/MM/scripting<br />
|Accessible UI<br />
|Nottingham<br />
|[[Image: Moko.jpg|center]]<br />
|-<br />
|[[User:mazileen|Al Johnson]]<br />
|Various<br />
|NX Client, VoIP<br />
|Derby<br />
|FreeRunner<br />
|}<br />
<br />
<br />
See [[Talk:Openmoko_Local_Groups:_East_Midlands|discussion]]<br />
<br />
[[Category:Openmoko Local Groups]]</div>DolfjeBot1http://openmoko.org/wiki/Openmoko_Local_Groups:_DuesseldorfOpenmoko Local Groups: Duesseldorf2008-08-31T12:51:49Z<p>DolfjeBot1: Replacing 'Freerunner' with 'FreeRunner'</p>
<hr />
<div>=== Possible Participants ===<br />
{|border=1<br />
!Name<br />
!Skills<br />
!Level of Interest<br />
!Location<br />
!Other<br />
!Has Device<br />
!Has Debug Board<br />
|-<br />
|[[User:Samon007|Lix]]<br />
|System Administrator, Scripting<br />
|I've ordered a GTA01Bv4 together with a friend from University. I like to pimp it to a network tool, showing CDP messages, doing pings and telnet maybe a sniffer if that will not be banned by law in a few weeks<br />
|Düsseldorf<br />
|willing to organize stuff i.e. meeting location/whatever. [[User_talk:Samon007|talk to me]].<br />
|<br />
|<br />
|-<br />
| [[User:Risto|Risto]]<br />
| Assembler, C, C++<br />
| Learning how OpenSource software works, contributing to OpenSource<br />
| Bocholt<br />
|<br />
| [[Image: Moko.jpg|center]]<br />
| [[Image: MokoBox.jpg|center]]<br />
|-<br />
| [[User:danielmewes|Daniel Mewes]]<br />
| C++, some system level Linux experience<br />
| I just ordered a phase 1 Neo, since I always had the vision of a phone where software and hardware are not bundled together. Also want to take the chance to participate in a somewhat bigger open source project.<br />
| Ratingen<br />
|<br />
|<br />
|<br />
|-<br />
| [[User:klinux|Klinux]]<br />
| Assembler, C, C++, shell scripting, Linux<br />
| Would like to contribute to the project, interested in getting basic phone functionality working from UI and maybe help integrating a web browser.<br />
| Düsseldorf<br />
| Just received my Neo and successfully made a phone call :-)<br />
|<br />
|<br />
|-<br />
|[[User:emdete|emdete]]<br />
| Developer; C, Python, Shellskripting, Java skills<br />
| Will test low-level services like gsm daemon with a different application<br />
| Düsseldorf<br />
| Interested in apps using directfb, different mobile phone software aproach, Openmoko on the greenphone.<br />
| [[Image: Moko.jpg|center]]<br />
|<br />
|-<br />
| [[User:Mac2k|mac2k]]<br />
| linux user<br />
| <br />
| Gerresheim<br />
|<br />
|<br />
|<br />
|-<br />
| [[User:l0ll|L0ll]] <br />
| a little bit Pascal and Linux<br />
| Learn a bit about open-source and of course i want to have a nice phone <br />
| Woppenroth<br />
| waiting for the FreeRunner :)<br />
|<br />
|<br />
|-<br />
| [[User:Quix0r|Quix0r]] <br />
| PHP5, Linux (since 1999), Bash scripting, ...<br />
| Want to replace his prohibitory against a free one. My wife and I still needs to move to Krefeld.<br />
| Uetersen near Hamburg<br />
| Waiting for the FreeRunner. :-)<br />
|<br />
|<br />
|-<br />
| [[User:MoR4euZ|MoR4euZ]] <br />
| linux user<br />
| <br />
| Essen<br />
| Waiting for the FreeRunner<br />
|<br />
|<br />
|-<br />
|...<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|}<br />
<br />
=== Meetings, Events ===<br />
Meeting language is German ;-)<br />
{|border=1<br />
!Date<br />
!Location<br />
!Topic<br />
!Who<br />
|-<br />
|[[OMLG-Duesseldorf_Meeting_20070823|23.08.2007, 17:00 UTC (19:00 CEST)]]<br />
|[http://www.destille-duesseldorf.de/ Destille Düsseldorf]<br />
|First GTA01Bv4 impressions for P1 owners and those who have no Neo yet. Giving each other a helping hand getting started.<br />
|[[User:Samon007|Lix]], [[User:emdete|emdete]], [[User:Risto|Risto]], ...<br />
|-<br />
|somewhere in 2008...<br />
|to be done<br />
|Is there any interest to meet again and talk about news?<br />
|<br />
|}<br />
<br />
[[Category:Openmoko Local Groups]]</div>DolfjeBot1http://openmoko.org/wiki/Openmoko_Local_Groups:_DortmundOpenmoko Local Groups: Dortmund2008-08-31T12:51:39Z<p>DolfjeBot1: Replacing 'Freerunner' with 'FreeRunner'</p>
<hr />
<div>=== Possible Participants ===<br />
{|border=1<br />
!Name<br />
!Skills<br />
!Level of Interest<br />
!Location<br />
!Other<br />
!Has Device<br />
!Has Debug Board<br />
|-<br />
|[[User:Ugh|ugh]]<br />
|Software Developer<br />
|Got my FreeRunner. Checking it out, getting started.<br />
|Dortmund<br />
|/*no comment*/<br />
|[[Image: Moko.jpg|center]]<br />
|<br />
|-<br />
|[[User:tobyS|TobyS]]<br />
|Software Developer<br />
|Owning a FreeRunner. Several more or less crazy development ideas.<br />
|Dortmund<br />
|Member of the PHP Usergroup (see below)<br />
|[[Image: Moko.jpg|center]]<br />
|<br />
|}<br />
<br />
=== Intermediate meeting point ===<br />
<br />
Several members of the local [http://phpugdo.de PHP Usergroup] own a FreeRunner and are intetressted in developing applications for it and sharing experiences about usage and development. If you want to meet other Openmoko enthusiasts, don't hesitate to drop by the [http://phpugdo.de/dabei_sein.html regular meeting], which takes place every Thursday from 18:30 in the [http://www.hicc-up.de/ HiccUp] bar/restaurant. Don't forget to bring your FreeRunner and/or notebook (wifi and power available). More detailed information on the [http://phpugdo.de PHP Usergroup Dortmund] website.<br />
<br />
[[Category:Openmoko Local Groups]]</div>DolfjeBot1http://openmoko.org/wiki/Openmoko_Local_Groups:_Central_TexasOpenmoko Local Groups: Central Texas2008-08-31T12:51:26Z<p>DolfjeBot1: Replacing 'Freerunner' with 'FreeRunner'</p>
<hr />
<div>Welcome to the Central Texas openmoko page!<br />
<br />
We have a mailing list. Join our group to meet other local Openmoko users. Details here: http://groups.google.com/group/austin-openmoko-users<br />
<br />
This group is for Austin/Round Rock and surrounding areas. Hopefully we'll be able to organize an event for when a few of us get the neos. Local LUGs will probably be interested too, update here as it happens.<br />
<br />
{|border=1<br />
!Name<br />
!Skills<br />
!Level of Interest<br />
!Location<br />
!Other<br />
|-<br />
|[[User:Weez|weez]]<br />
|C++, C#, Perl, bone dissolve soft palm, toad force level4 <br />
|neo1973 SH1 on the way<br />
|Austin<br />
|Finally<br />
|-<br />
|[[User:Eugeneoden|eugeneoden]]<br />
|C, python, telephony (VoIP & PSTN)<br />
|received GTA01 last week<br />
|Austin<br />
|researching VoIP possibilities on neo1973<br />
|-<br />
|[[User:Dalnefre|dalnefre]]<br />
|C, Java, embedded kernel design<br />
|waiting for FreeRunner availability<br />
|Austin<br />
|Interested in collaborative development<br />
|}<br />
<br />
<br />
<br />
See [[Talk:Openmoko_Local_Groups:_Central_Texas|discussion]]<br />
<br />
[[Category:Openmoko Local Groups]]</div>DolfjeBot1http://openmoko.org/wiki/Openmoko_Local_Groups:_BirminghamOpenmoko Local Groups: Birmingham2008-08-31T12:51:13Z<p>DolfjeBot1: Replacing 'Freerunner' with 'FreeRunner'</p>
<hr />
<div>Welcome to the Birmingham openmoko page!<br />
<br />
Hopefully we'll be able to organise an event for when a few of us get the neos - please also keep the page updated with any interest you get from your local LUGs.<br />
<br />
{|border=1<br />
!Name<br />
!Skills<br />
!Level of Interest<br />
!Location<br />
!Other<br />
|Has?<br />
|-<br />
|Andy Loughran<br />
|Learning Python<br />
|On the lists since January, bought the neo1973 on the 9th July<br />
|Solihull<br />
|Got the neo and currently demonstrating to Vodafone UK Handset Procurement.<br />
|[[Image: Moko.jpg|center]]<br />
|-<br />
|Giles Jones<br />
|C programming<br />
|Development of interface, applications, core libraries<br />
|Cannock, Staffs (near enough to brum)<br />
|Hopefully get my phone soon, can't get the emulator networking working<br />
|-<br />
|Greg Clarke<br />
|Sysadmin<br />
|User and integration of webapps with mobile devices<br />
|Another one in Cannock, Staffs <br />
|My FreeRunner arrived 26 Jun :) <br />
|[[Image: Moko.jpg|center]]<br />
|}<br />
<br />
<br />
<br />
See [[Talk:Openmoko_Local_Groups:_Birmingham|discussion]]<br />
[[Category:Openmoko Local Groups]]</div>DolfjeBot1http://openmoko.org/wiki/Openmoko_Local_Groups:_BerlinOpenmoko Local Groups: Berlin2008-08-31T12:51:03Z<p>DolfjeBot1: Replacing 'Freerunner' with 'FreeRunner'</p>
<hr />
<div>See [[Talk:Openmoko_Local_Groups:_Berlin|discussion]]<br />
<br />
=== Mailing list ===<br />
We have set up a mailinglist a freelists.org. To subscribe either send a mail with the topic 'subscribe' to openmoko-users-berlin-request@freelists.org OR through the web interface: http://www.freelists.org/list/openmoko-users-berlin.<br />
<br />
=== Possible Participants ===<br />
{|border=1<br />
!Name<br />
!Skills<br />
!Level of Interest<br />
!Location<br />
!Other<br />
!Has Device<br />
!Has Debug Board<br />
|-<br />
|[[User:Minime|tim]]<br />
|mostly web related<br />
|No GTA01Bv4, waiting for GTA02. <br />
|berlin.nord<br />
|willing to organize stuff i.e. meeting location/whatever. [http://wiki.openmoko.org/index.php?title=User_talk:Minime&action=edit&section=new talk to me], or e-mail: OM DOT 5 DOT minime@xoxy.net<br />
|<br />
|<br />
|-<br />
|[[User:spag|spag]]<br />
|too lazy<br />
|patiently waiting for GTA02 with WLAN<br />
|Marzahn<br />
|I'm interested in VoIP applications on Openmoko.<br />
|<br />
|<br />
|-<br />
|[[User:PH5|pH5]]<br />
|Coding, RE, Uni<br />
|Openmoko, gsmd, GTA01, Magician<br />
|Zehlendorf<br />
|[http://projects.linuxtogo.org/projects/sphyrna Sphyrna]<br />
|[[Image:Moko.jpg|center]]<br />
|<br />
|-<br />
|[[User:Barmeier|barmeier]]<br />
|Coding in C and Java<br />
|GTA01, Magician<br />
|Steglitz<br />
|I'am interested in Sync, application integration and usability improvements<br />
|<br />
|<br />
|-<br />
|[[User:Kriss|kriss]]<br />
|Coding<br />
|<br />
|Wedding<br />
|<br />
|[[Image:Moko.jpg|center]]<br />
|[[Image:MokoBox.jpg|center]]<br />
|-<br />
|[[User:Roh|roh]]<br />
|hw, sw<br />
|<br />
|mitte/pberg<br />
|access to schematics<br />
|GTA01bv4, GTA02v5, etc[[Image:Moko.jpg|center]]<br />
|[[Image:MokoBox.jpg|center]]<br />
|-<br />
|[[User:proquar|chris]]<br />
|travelling in time and space<br />
|abusing the freerunner in every way imaginable<br />
|Wedding<br />
|Anyone in interested in group-order? see: http://lists.openmoko.org/pipermail/community/2008-April/015080.html at the bottom<br />
|<br />
|<br />
|-<br />
|[[User:einalex|einalex]]<br />
|Coding, TU, cooking, soldering<br />
|FreeRunner, syncing<br />
|Hamburg / Frankfurt / München<br />
|If you decide to order a 10pack I'd like to join the fun. Contact me at my email address alexander dot gabriel at tuhh dot de<br />
|<br />
|<br />
|-<br />
|[[User:fischel|fischel]]<br />
|php, java, triathlon<br />
|FreeRunner<br />
|Charlottenburg<br />
|interested in group-order<br />
|A780<br />
|<br />
|-<br />
|[[User:Torsten_Grote|Torsten]]<br />
|coding, ui<br />
|testing, minor coding, meeting<br />
|Griebnitzsee<br />
|let's initiate local user group meetings<br />
|[[Image:Moko.jpg|center]] gta02v5<br />
|<br />
|-<br />
|[[User:govindas|govindas]]<br />
|perfect DAU simulator.<br />
|freerunner, meetings <br />
|Friedrichshain<br />
|group order<br />
|<br />
|<br />
|-<br />
|[[User:philippt|philippt]]<br />
|coding (java, python, perl, bash), linux stuff<br />
|want to have a really smart phone<br />
|Friedrichshain<br />
|interested in group order, knowledge sharing and real-life experience with freerunner<br />
|<br />
|<br />
|-<br />
|[[User:ogai|ogai]]<br />
|coding (java, groovy), linux stuff<br />
|want to have a really smart phone<br />
|Prenzlauer Berg<br />
|interested in group order, knowledge sharing and real-life experience with freerunner<br />
|[[Image:Moko.jpg|center]] gta02<br />
|<br />
|-<br />
|[[User:carcinoma|carcinoma]]<br />
|coding (c++, progress), linux, Design<br />
|free me from proprietary tools<br />
|Weissen See (Pankow)<br />
|interested in knowledge sharing, freetime usage, usage in Job/Professional<br />
|Get GTA02 from Pulster, next big order will be mine(25.7.)<br />
|<br />
|-<br />
|[[User:Ott--|ott--]]<br />
|coding, Linux, even Windows<br />
|I want to be free<br />
|Schmöckwitz (Köpenick)<br />
|[http://picasaweb.google.com/Joachim.Ott/NeoFreeRunner see pics]<br />
|GTA02v5 [[Image:Moko.jpg|center]]<br />
|<br />
|-<br />
|[[User:dk|dk]]<br />
|java<br />
|Gta02<br />
|moabit<br />
|interested in group order<br />
|<br />
|<br />
|-<br />
|[[User:relet|relet]]<br />
|code<br />
|would read your feed<br />
|moabit<br />
|<br />
|02<br />
|nak<br />
|-<br />
|[[User:Sbusch|sbusch]]<br />
|coding (c, c++, java), linux<br />
|coding on my free phone :-)<br />
|Friedrichshain<br />
|especially interested in voip and IM<br />
|<br />
|<br />
|-<br />
|[[User:thebohemina|thebohemian]]<br />
|C, Java, OpenEmbedded, organize things<br />
|OM for professional use, sharing knowledge, Free Software advocacy<br />
|Friedrichshain<br />
|<br />
|GTA02, GTA01<br />
|yes|-<br />
|-<br />
|[[User:Su2|Stephan]]<br />
|coding (c, c++), linux<br />
|OM for fun, personal use, Free Software advocacy<br />
|Friedrichshain<br />
|interested in local user group meetings<br />
|not yet, ordered GTA02<br />
|<br />
|-<br />
|[[User:VanInwagen|vanInwagen]]<br />
|java, linux<br />
|OM only for having it<br />
|Biesdorf<br />
|interested in group order as well, even two OMs<br />
|unfortunately not yet<br />
|<br />
|-<br />
|...<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|}<br />
<br />
=== Meetings, Events ===<br />
Meeting language is German ;-)<br />
{|border=1<br />
!Date<br />
!Location<br />
!Topic<br />
!Who<br />
|-<br />
|every wednesday / 20:00<br />
|[http://wiki.c-base.org/coredump/WaveLoeten c-base (zusammen mit dem Freifunkertreffen)]<br />
|FreeRunner Release / Hands On<br />
|See [[Talk:Openmoko_Local_Groups:_Berlin|discussion]]<br />
|-<br />
|23.08.2007 / 18:00<br />
|[https://berlin.ccc.de/wiki/CCC_Berlin CCCB] / [https://berlin.ccc.de/wiki/Club_Discordia Club Diskordia]<br />
|First meeting. bring your hardware<br />
|Roh, pH5, [[User:Minime|tim]](+ 2?), ? (please add yourself)<br />
|-<br />
|8.-12. August 2007<br />
|Flugplatz Finowfurt<br />
|[https://events.ccc.de/camp/2007/Intro/ Chaos Communication Camp 2007] und [http://events.ccc.de/camp/2007/GSM_Village GSM Village]<br />
|?<br />
|}<br />
<br />
[[Category:Openmoko Local Groups]]</div>DolfjeBot1http://openmoko.org/wiki/Openmoko_Local_Groups:_AntwerpOpenmoko Local Groups: Antwerp2008-08-31T12:50:53Z<p>DolfjeBot1: Replacing 'Freerunner' with 'FreeRunner'</p>
<hr />
<div> See [[Talk:Openmoko_Local_Groups:_Antwerp|discussion]]<br />
<br />
{|border=1<br />
!Name<br />
!Skills<br />
!Level of Interest<br />
!Location<br />
!Other<br />
|-<br />
|[[User:Steamrunner|Steamrunner]]<br />
|electronics, Linux, VoIP, programming<br />
|Neo1973 - GTA01 (Base) Owner<br />
|2660 Hoboken (Antwerpen)<br />
|willing to organize meetings, brainstorming, workshops, whatever. talk to me.<br />
|-<br />
|[[User:BioGeek|BioGeek]]<br />
|bioinformatics, Linux user since 1998, Python programming<br />
|Awaiting NeoFreeRunner, Mobistar<br />
|2018 Antwerpen (Berchem)<br />
|willing to meet other Openmoko users, exchange ideas and spread the love for Free and Open Source Software in general<br />
|}<br />
[[Category:Openmoko Local Groups]]</div>DolfjeBot1http://openmoko.org/wiki/OpenmokoFramework/Status_Update_3OpenmokoFramework/Status Update 32008-08-31T12:50:25Z<p>DolfjeBot1: Replacing 'Freerunner' with 'FreeRunner'</p>
<hr />
<div>=Openmoko Framework Team Status Report 2008.7.1=<br />
<br />
Hi guys! This is the third Openmoko Framework Team Status update, featuring our second milestone release and more.<br />
<br />
For the general motivation, the goals, and the way we are doing our work, please see http://wiki.openmoko.org/wiki/OpenmokoFramework.<br />
<br />
== What happened since the last report ==<br />
<br />
=== People ===<br />
<br />
* John Lee <john_lee@openmoko.com> joined the framework team and will help us part time -- welcome on board, John!<br />
<br />
=== DBus APIs ===<br />
<br />
* org.freesmartphone.GSM is almost complete now and stable. We did only minor corrections and enhancements based on client feedback.<br />
* Preliminary versions of org.freesmartphone.Device.Audio and .Accelerometer have been added.<br />
* org.freedesktop.Gypsy has been implemented and org.freesmartphone.GPS will be used to configure more obscure GPS features<br />
* Still brainstorming about org.freesmartphone.Preferences and org.freesmartphone.Context.<br />
<br />
=== Implementations ===<br />
<br />
'''Openmoko Framework Image -- 'All good things' (Milestone II)'''<br />
<br />
This is the second milestone release of the framework and the framework testing application 'Zhone'.<br />
<br />
====Purpose====<br />
<br />
A lightweight image that turns an Openmoko phone into a featurephone and that can serve as the basis for further application development using the freesmartphone.org dbus APIs.<br />
<br />
==== What's new since Milestone I ====<br />
<br />
'''Note: These are only the highlights. See the [http://git.freesmartphone.org gitweb] commit logs for the gory details...'''<br />
<br />
* General<br />
** Merged individual daemons into one daemon with multiple subsystems<br />
** Converted to python logging for debugging<br />
** Enhanced tests and API documentation<br />
<br />
* odevice<br />
** Implements org.freesmartphone.Device.Audio (GStreamer Playback engine and alsa scenario control)<br />
** Implements org.freesmartphone.Device.Input (button switches / headphones insertion etc.)<br />
** Accellerator support (raw data, gestures coming soon)<br />
<br />
* ogsmd (''renamed from ophoned'')<br />
** Implements org.freesmartphone.GSM.PDP (GPRS handling)<br />
** Implements org.freesmartphone.GSM.CB (Cell Broadcast handling)<br />
** Implements org.freesmartphone.GSM.HZ (O2/Genion Home Zone handling)<br />
** Multiparty call handling for TI Calypso<br />
** Initial support for Freescale Neptune Modem and Sierra Modem<br />
** Call forwarding<br />
** DTMF<br />
<br />
* opgsd (''new subsystem'')<br />
** Implements the org.freedesktop.Gypsy DBus API<br />
** Supports U-Blox binary protocol<br />
<br />
* ophoned (''new subsystem'')<br />
** Prepare combined telephony API for VoIP and GSM<br />
<br />
* zhone<br />
** Add phonebook<br />
** Add messagebook<br />
** Add basic GPS viewer<br />
** Integrate Illume launcher and keyboard<br />
** Ship additional programs<br />
<br />
====Download / Installation====<br />
<br />
# Grab a uImage and a .jffs2 for your device from http://downloads.openmoko.org/framework/milestone2/.<br />
# Flash it to your Neo1973 (om-gta01) or NeoFreeRunner (om-gta02) with dfu-util.<br />
# Boot and wait until the Zhone main window appears.<br />
# Have fun.<br />
<br />
====What you can expect from this release====<br />
<br />
* Telephony<br />
* Phonebook<br />
* Messagebook (SMS)<br />
* GPS<br />
* frameworkd implementing the following dbus APIs:<br />
** org.freesmartphone.Device.{Audio|Input|IdleNotifier|PowerSupply|Display|LED}<br />
** org.freesmartphone.Usage<br />
** org.freesmartphone.Event<br />
** org.freesmartphone.GSM.{Device|SIM|Network|PDP|CB|HZ}<br />
** org.freedesktop.Gypsy<br />
<br />
====What we expect from you====<br />
<br />
* Feedback and comments for the dbus APIs. This is your chance to take an active role into shaping the application programming interface for all your cool applications.<br />
<br />
* Focus on using the services. Zhone is just our testing-UI and bears little functionality. It's the services that matter.<br />
<br />
* The best way to interact with the framework is by exploring the dbus APIs. For that you can use the two tools, which are already installed:<br />
** [[OpenmokoFramework/mdbus|mdbus]] -- a dbus introspection and interaction utility,<br />
** [[OpenmokoFramework/cli|cli-framework]] -- a python dbus command line interface.<br />
<br />
* If you want to interact with the GSM modem, while the frameworkd is running, you can use [[OpenmokoFramework/mickeyterm|mickeyterm]] -- a MUXer-aware minimal terminal emulator.<br />
<br />
===What's next===<br />
<br />
* SMS PDU Handling<br />
* GTA01 GPS integration, cold and warm start improvements<br />
* Preferences integration<br />
* More tutorials and high level documentation<br />
* Work towards Milestone 3 (see [http://trac.freesmartphone.org Roadmap and Issue Tracker])<br />
<br />
==The Team==<br />
<br />
Mickey, Jan, Daniel, Guillaume, John. <br />
<br />
[[Category:Framework]]<br />
[[Category:Community Update]]</div>DolfjeBot1http://openmoko.org/wiki/OpenmokoFramework/Status_Update_2OpenmokoFramework/Status Update 22008-08-31T12:50:15Z<p>DolfjeBot1: Replacing 'Freerunner' with 'FreeRunner'</p>
<hr />
<div>=Openmoko Framework Team Status Report 2008.6.1=<br />
<br />
Hi guys! This is the second Openmoko Framework Team Status update, today only brief and focusing our first milestone release.<br />
<br />
For the general motivation, the goals, and the way we are doing our work, please see http://wiki.openmoko.org/wiki/OpenmokoFramework.<br />
<br />
== What happened since the last report ==<br />
<br />
=== People ===<br />
<br />
* Daniel Willmann <alphaone@openmoko.org> joined the framework team -- welcome on board, Daniel!<br />
<br />
=== DBus APIs ===<br />
<br />
* org.freesmartphone.GSM has received slight corrections and enhancements based on feedback during implementing ophoned and gsmd2.<br />
* org.freesmartphone.{Event|Usage|Device} start looking more stable.<br />
* We have started brainstorming about org.freesmartphone.Preferences and org.freesmartphone.Context<br />
<br />
=== Implementations ===<br />
<br />
'''Openmoko Framework Image -- 'Groundhog Day' (Milestone I)'''<br />
<br />
This is the first milestone release of the framework and the framework testing application 'Zhone'.<br />
<br />
====Purpose====<br />
<br />
A lightweight image that turns an Openmoko phone into a featurephone and that serves as the basis for further application development experiments using the freesmartphone.org dbus APIs.<br />
<br />
====Download / Installation====<br />
<br />
# Grab a uImage and a .jffs2 for your device from http://downloads.openmoko.org/framework/milestone1/.<br />
# Flash it to your Neo1973 (om-gta01) or NeoFreeRunner (om-gta02) with dfu-util.<br />
# Boot and wait until the 'Openmoko - Please wait...' appears.<br />
# ''Note: If the application does not start after 2 minutes, please reboot once. This can happen the first time you boot the framework image. It's a last-minute bug that crept in this milestone (sorry!).''<br />
<br />
====What you can expect from this release====<br />
<br />
* Simple Telephony (singleparty calls).<br />
* First release of the following freesmartphone.org dbus APIs:<br />
** org.freesmartphone.Device<br />
** org.freesmartphone.Usage<br />
** org.freesmartphone.Event<br />
** org.freesmartphone.GSM<br />
<br />
====What you should not expect====<br />
<br />
* 100% working Suspend and Resume all the time (kernel issues are still being worked on.<br />
* Anything beyond simple telephony. This will come in future milestones.<br />
<br />
====What we expect from you====<br />
<br />
* Feedback and comments for the dbus APIs. This is your chance to take an active role into shaping the application programminginterface for all your cool applications.<br />
<br />
===What's next===<br />
<br />
* Enhancing the API documentation, e.g. org.freesmartphone.GSM at http://www.freesmartphone.org/index.php/Standards/OpenPhoneServerAPI<br />
* Working towards Milestone 2 (see [[OpenmokoFramework|http://wiki.openmoko.org/wiki/OpenmokoFramework]])<br />
<br />
==The Team==<br />
<br />
Mickey, Jan, Daniel, Guillaume. <br />
<br />
:M:<br />
<br />
[[Category:Framework]]<br />
[[Category:Community Update]]</div>DolfjeBot1http://openmoko.org/wiki/Om_2008.8Om 2008.82008-08-31T12:49:41Z<p>DolfjeBot1: Replacing 'Freerunner' with 'FreeRunner'</p>
<hr />
<div>{{Languages|Om 2008.8}}<br />
{{Om 2008.8}}<br />
<br />
{{Distributions|Om 2008.8}}<br />
<br />
== Summary ==<br />
<br />
'''Om 2008.8''' is the successor to [[Om 2007.2]] and had '''ASU''' as a codename. It was [http://lists.openmoko.org/pipermail/community/2008-August/025619.html released] on '''August 08, 2008''' (+ update "stable" releases starting from '''August 26, 2008'''). Om 2008.8 uses EFL for the launcher, custom UI applications and [[QtopiaOnX11|Qtopia on X11]] for telephony. The distribution is the first step from GTK+ on x11 to using multiple toolkits in combination.<br />
<br />
== What's New ? ==<br />
<br />
Compared to 2007.2 that has a longer development history, Om 2008.8 is definitely a .0 major release. So think KDE 4.0 vs. 3.5, not Linux 2.6.23 vs. 2.6.22. If you want the stability level required to use the FreeRunner as your main phone, it is suggested for now to keep 2007.2 in the phone's flash memory and test 2008.8 on a removable SD card.<br />
<br />
The main user-visible changes:<br />
<br />
* The user interface has been fully revised with a new window manager [[illume]]. It is visually much richer, and can be customized further by using your own [[Edje]] files.<br />
* '''[[Om2008.8_Installer|A graphical installer]]''' allows to add easily new applications, themes and functionality.<br />
* A new [[Om2008.8_Locations|Locations]] application is provided, to save your favorite spots and share them with friends via sms.<br />
* Power management has been improved: The Aux button now locks the screen, the Power button suspends and the red LED behind the Aux button lights up when charging.<br />
* The [[Om2008.8_Keyboard| keyboard]] is now the Qtopia one (whether this is an improvement has been [[Keyboard_Debate|hotly debated]]).<br />
<br />
For developers, the main changes are:<br />
* Multiple toolkits: '''Om 2008.8''' supports [http://www.enlightenment.org/ EFL], [http://trolltech.com/products/qtopia Qtopia] and [http://www.gtk.org GTK+] applications.<br />
* A [[CommunityRepository| Community Repository]] has been set up, it is integrated in the ([[Om2008.8_Installer|Installer]]).<br />
* '''Source Codes''' are publicly available, allowing for customization all the way down to low level systems.<br />
<br />
For more details, see the [[Om 2008.8 Guide]] and the [[Om2008.8 Feature Plan|Om 2008.8 Feature Plan]].<br />
<br />
<br />
{| class="wikitable" cellspacing="2" cellpadding="2" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; width:100%;floating="center"; "<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #222222; width:33% " |<br />
[[Image:Om2008 home.png|200px|center]]<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #222222; width:33% " |<br />
[[Image:Installer4.png|200px|center]]<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #222222; width:33% " |<br />
[[Image:Om2008 installer1.png|200px|center]]<br />
|-<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #222222; width:33% " | <br />
[[Image:Main.png|200px|center]]<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #222222; width:33% " |<br />
[[Image:Edit1.png|200px|center]]<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #222222; width:33% " |<br />
[[Image:Om locations4.png|200px|center]]<br />
|}<br />
<br />
<br />
<!---the following anchor is here to ensure that the "Download" link at http://openmoko.com/download.html links to the correct section. please don't delete the anchor unless that link is changed or removed---><br />
<span id="Flash_Om_2008.8_images"></span><br />
<br />
== Installation ==<br />
<br />
To install the Om2008.8 stable distribution on the Neo FreeRunner, download the Root Filesystem and the Kernel image files from [[Download]] page and install according to [[Flashing the Neo FreeRunner]]. Note that flashing the smartphone will overwrite all your existing data and software.<br />
<br />
== Known Issues ==<br />
<br />
This is only a subset. See [http://docs.openmoko.org/trac/search?q=2008.8 all tickets with 2008.8] in the bug tracker.<br />
<br />
'''GSM'''<br />
<br />
* [http://docs.openmoko.org/trac/ticket/1766 Cannot make calls or receive SMS messages]<br />
* [http://docs.openmoko.org/trac/ticket/1662 GSM not working properly after x hours]<br />
<br />
'''WiFi'''<br />
<br />
* [http://docs.openmoko.org/trac/ticket/1625 WiFi can only connect once]<br />
* [http://docs.openmoko.org/trac/ticket/1734 WiFi shows up unknown] is caused by hald not running, which can be fixed by removing <tt>/etc/volatile.cache</tt> and rebooting<br />
<br />
'''Audio quality'''<br />
<br />
* [http://docs.openmoko.org/trac/ticket/1640 Improve overall audio]<br />
<br />
'''System Software''' <br />
<br />
* [http://docs.openmoko.org/trac/ticket/1736 Boot screen goes into sleep and never wake up if not touch during booting]<br />
* [http://docs.openmoko.org/trac/ticket/1597 After long suspend, kernel thread events]<br />
* [http://docs.openmoko.org/trac/ticket/1315 xglamo: performance decreases after a while]<br />
* [http://docs.openmoko.org/trac/ticket/1682 Neo turns off before reaching x]<br />
<br />
'''Networking'''<br />
* No Updates/Installation are possible or pings to domains because DNS is not working. This problem occurs because the /etc/resolv.conf is empty by default.<br />
Add these lines in /etc/network/interfaces:<br />
<br />
up echo nameserver 208.67.222.222 > /etc/resolv.conf<br />
up echo nameserver 208.67.220.220 >> /etc/resolv.conf<br />
This is to be inserted below gateway address and above the bluetooth networking. After this it will be set on every reboot.<br />
<br />
For resolving DNS without restarting, run the following commands:<br />
<br />
echo nameserver 208.67.222.222 > /etc/resolv.conf<br />
echo nameserver 208.67.220.220 >> /etc/resolv.conf<br />
This should solve most of your moko side networking issues. If you need any other help please refer to [[USB Networking]]<br />
<br />
{{note| [http://en.wikipedia.org/wiki/Resolvconf resolvconf] is installed so should probably be used <br />
<br />
'''Problem''': parts of resolvconf are missing: without the scripts under /etc/network/if-{up,down}.d, and /etc/resolvconf/run/enable-updates and /lib/resolvconf/list-records it does nothing, and even then, /etc/resolvconf/run should probably be a symlink to /var/run, or /etc/resolv.conf needs to be pointed at /etc/resolvconf/run/resolv.conf -- once all that's done, it seems to work as long as you add something like this to /etc/network/interfaces at the end of the usb0 stanza:<br />
<br />
dns-nameservers 192.168.0.200<br />
dns-search example.com<br />
<br />
and add <tt>usb*</tt> above <tt>eth*</tt> in <tt>/etc/resolvconf/interface-order</tt><br />
<br />
}}<br />
<br />
{{Note| '''Solution:''' Steps to add missing resolvconf script: <br><br />
<code>touch /etc/resolvconf/run/enable-updates</code><br><br />
<code>cd /etc ; rm resolv.conf ; ln -s /etc/resolvconf/run/resolv.conf .</code><br><br />
<code>mkdir /lib/resolvconf/ ; cd /lib/resolvconf/</code><br><br />
<code><nowiki>wget http://kopparv34.mine.nu/list-records</nowiki></code><br><br />
<code>chmod +x list-records</code><br><br />
Edit <code>/etc/network/interfaces</code> and remove the lines:<br><br />
<code> network 192.168.0.0</code><br><br />
<code> gateway 192.168.0.200</code><br><br />
If we need to use the usb network more then just locally from the computer in the other end of the USB-cable, login with ssh and add a default route like this:<br><br />
<code>route add default gateway 192.168.0.200</code><br />
}}<br />
<br />
* Usb-networking will not work until rebooted after initial boot.<br />
<br />
'''Usability''' <br />
<br />
* The Pin-Dialog by default just shows letters. You have to slide your finger up/down over the keyboard to make the numbers/uppercase/special characters appear.<br />
* The installer app doesn't release administrative rights which results in not being able to use opkg. Solution: run "killall packagekitd" (on the freerunner or when ssh'ed in).<br />
* The installer app doesn't release administrative rights which results in not being able to use opkg. Alternate Solution: On the FreeRunner, use the drop-down menu to close all open applications.<br />
* The keyboard may not be adapted for all uses. See [[Keyboard Debate]] for a full discussion and options.<br />
<br />
== Official updates for "stable" Om 2008.8 ==<br />
<br />
Posterior to the Om2008.8 release made on 2008/08/08, development of ASU/Om2008.8 is switching to a Debian-like model with three branches: stable, testing and unstable ([http://lists.openmoko.org/pipermail/community/2008-August/026491.html see this message] for more details).<br />
<br />
Official updates for the "stable" branch are now available (as of 2008/08/26) in two forms (see [http://lists.openmoko.org/pipermail/community/2008-August/027997.html see this message] for the announcement) :<br />
* in the http://downloads.openmoko.org/repository/Om2008.8/ opkg feeds (which should already be configured for opkg updates in 2008.8),<br />
* as flash-able images in http://downloads.openmoko.org/releases/Om2008.8-update/<br />
<br />
The changelog of the stable branch can be ogtained here : http://git.openmoko.org/?p=openmoko.git;a=log;h=org.openmoko.asu.stable<br />
<br />
== Dedication ==<br />
<br />
<pre><br />
From: Openmoko<br />
To: openmoko-community mailing list<br />
<br />
Om 2008.8 was designed to be empty, for the very purpose of showcasing your ideas.<br />
<br />
Think of our products as galleries. We're building the environment.<br />
Each one different from the next. You'll get all the free art supplies<br />
you could imagine because we want you to add your own meaning.<br />
You choose: consume, create, or both.<br />
<br />
Either way you create your own meaning. It's about you.<br />
</pre><br />
<br />
[[Category:Openmoko]]<br />
[[Category:Om 2008.8]]</div>DolfjeBot1http://openmoko.org/wiki/Neo_alsamixerNeo alsamixer2008-08-31T12:49:10Z<p>DolfjeBot1: Replacing 'Freerunner' with 'FreeRunner'</p>
<hr />
<div>The purpose of this page is to describe the Neo's alsamixer settings.<br />
<br />
===Run===<br />
To run alsamixer through ssh, run<br />
alsamixer<br />
===Use===<br />
* Esc - exit<br />
* F1 - help<br />
* F2 - info<br />
* F3 - playback controls<br />
* F4 - capture controls<br />
* F5 - all controls<br />
* Tab - toggle view<br />
* Space - toggle capture<br />
* m - toggle mute<br />
* < > - mute left/right<br />
* Up/Down - increase/decrease volume<br />
* Left/Right - channel scroll<br />
<br />
<br />
===Settings Descriptions===<br />
{| border=1 |<br />
| '''Setting''' || '''playback''' or '''capture''' || '''Channels''' (1,2, or toggle) || '''Description'''<br />
|-<br />
| Headphone || Playback || 2 || playback volume on the headphones (headset)<br />
|-<br />
| Headphone Playback ZC || Playback || || <br />
|-<br />
| Bass || Playback || || <br />
|-<br />
| Bass Boost || Playback || || <br />
|-<br />
| Bass Filter || Playback || || <br />
|-<br />
| Treble || Playback || || <br />
|-<br />
| Treble Cutoff || Playback || || <br />
|-<br />
| PCM || Playback || || <br />
|-<br />
| Sidetone || Playback || || <br />
|-<br />
| Line Left Mux || Playback || || <br />
|-<br />
| Line Mixer || Playback || || <br />
|-<br />
| Line Mono Mux || Playback || || <br />
|-<br />
| Line Right Mux || Playback || || <br />
|-<br />
| Mic Selection Mux || Playback || || <br />
|-<br />
| Mic Sidetone Mux || Playback || || <br />
|-<br />
| Mono || Playback || || <br />
|-<br />
| Mono 2 Mux || Playback || || <br />
|-<br />
| Mono Bypass || Playback || || <br />
|-<br />
| Mono Mixer Bypass Playback Swit || Playback || || <br />
|-<br />
| Mono Mixer Left || Playback || || <br />
|-<br />
| Mono Mixer Right Playback Switc || Playback || || <br />
|-<br />
| Mono Mixer Sidetone Playback Sw || Playback || || <br />
|-<br />
| Mono Mixer Voice Playback Switc || Playback || || <br />
|-<br />
| Mono Playback ZC || Playback || || <br />
|-<br />
| Mono Sidetone || Playback || || <br />
|-<br />
| Mono Voice || Playback || || <br />
|-<br />
| Playback 6dB Attenuate || Playback || || <br />
|-<br />
| Playback Mixer Left Capture Swi || Playback || || <br />
|-<br />
| Playback Mixer Right Capture Sw || Playback || || <br />
|-<br />
| Playback Mixer Voice Capture Sw || Playback || || <br />
|-<br />
| Playback Mono Mix || Playback || || <br />
|-<br />
| Playback Phase || Playback || || <br />
|-<br />
| Capture 6dB Attenuate || Playback || || <br />
|-<br />
| Capture Filter || Playback || || <br />
|-<br />
| Capture Filter Cut-off || Playback || || <br />
|-<br />
| Capture Filter Select || Playback || || <br />
|-<br />
| Capture Left Mixer || Playback || || <br />
|-<br />
| Capture Left Mux || Playback || || <br />
|-<br />
| Capture Right Mixer || Playback || || <br />
|-<br />
| Capture Right Mux || Playback || || <br />
|-<br />
| Capture ZC || Playback || || <br />
|-<br />
| 3D || Playback || || <br />
|-<br />
| 3D Function || Playback || || <br />
|-<br />
| 3D Lower Cut-off || Playback || || <br />
|-<br />
| 3D Upper Cut-off || Playback || || <br />
|-<br />
| ADC Data Select || Playback || || <br />
|-<br />
| ALC Capture Attack Time || Playback || || <br />
|-<br />
| ALC Capture Decay Time || Playback || || <br />
|-<br />
| ALC Capture Function || Playback || || <br />
|-<br />
| ALC Capture Hold Time || Playback || || <br />
|-<br />
| ALC Capture Max || Playback || || <br />
|-<br />
| ALC Capture NG || Playback || || <br />
|-<br />
| ALC Capture NG Threshold || Playback || || <br />
|-<br />
| ALC Capture NG Type || Playback || || <br />
|-<br />
| ALC Capture Target || Playback || || <br />
|-<br />
| ALC Capture ZC || Playback || || <br />
|-<br />
| Amp Spk || Playback || || <br />
|-<br />
| Amp State || Playback || || <br />
|-<br />
| Bypass || Playback || || <br />
|-<br />
| DAI Mode || Playback || || <br />
|-<br />
| DAPM GSM Line In || Playback || || <br />
|-<br />
| DAPM GSM Line Out || Playback || || <br />
|-<br />
| DAPM Handset Mike || Playback || || <br />
|-<br />
| DAPM Handset Spk || Playback || || <br />
|-<br />
| DAPM Headset Mike || Playback || || <br />
|-<br />
| DAPM Stereo Out || Playback || || <br />
|-<br />
| De-emphasis || Playback || || <br />
|-<br />
| Left Mixer Bypass Playback Swit || Playback || || <br />
|-<br />
| Left Mixer Left || Playback || || <br />
|-<br />
| Left Mixer Sidetone Playback Sw || Playback || || <br />
|-<br />
| Left Mixer Voice Playback Switc || Playback || || <br />
|-<br />
| Out3 Mux || Playback || || <br />
|-<br />
| Out4 Mux || Playback || || <br />
|-<br />
| ROUT2 Phase || Playback || || <br />
|-<br />
| Right Mixer Bypass Playback Swi || Playback || || <br />
|-<br />
| Right Mixer Right Playback Swit || Playback || || <br />
|-<br />
| Right Mixer Sidetone Playback S || Playback || || <br />
|-<br />
| Right Mixer Voice Playback Swit || Playback || || <br />
|-<br />
| Rx Mixer || Playback || || <br />
|-<br />
| Speaker || Playback || || <br />
|-<br />
| Speaker Playback ZC || Playback || || <br />
|-<br />
| Voice || Playback || || <br />
|-<br />
| Bass || Capture || || <br />
|-<br />
| Treble || Capture || || <br />
|-<br />
| PCM || Capture || || <br />
|-<br />
| Sidetone || Capture || || <br />
|-<br />
| Mic1 || Capture || || <br />
|-<br />
| Mic2 || Capture || || <br />
|-<br />
| Capture || Capture || || <br />
|-<br />
| 3D || Capture || || <br />
|-<br />
| ADC || Capture || || <br />
|-<br />
| ALC Capture Attack Time || Capture || || <br />
|-<br />
| ALC Capture Decay Time || Capture || || <br />
|-<br />
| ALC Capture Hold Time || Capture || || <br />
|-<br />
| ALC Capture Max || Capture || || <br />
|-<br />
| ALC Capture NG Threshold || Capture || || <br />
|-<br />
| ALC Capture Target || Capture || || <br />
|-<br />
| ALC Mixer Line || Capture || || <br />
|-<br />
| ALC Mixer Mic1 || Capture || || <br />
|-<br />
| ALC Mixer Mic2 || Capture || || <br />
|-<br />
| ALC Mixer Rx || Capture || || <br />
|-<br />
| Voice Sidetone || Capture || || <br />
|-<br />
|}<br />
<br />
<br />
===Troubleshooting===<br />
See [[FreeRunner Hardware Issues#Better alsamixer settings]]<br />
<br />
[[Category:Audio]]</div>DolfjeBot1http://openmoko.org/wiki/Neo_FreeRunner_Hardware_IssuesNeo FreeRunner Hardware Issues2008-08-31T12:49:00Z<p>DolfjeBot1: Replacing 'Freerunner' with 'FreeRunner'</p>
<hr />
<div>{{Neo FreeRunner Menu}}<br />
<br />
This is a community-written page that discusses '''hardware issues''' with the FreeRunner/[[GTA02]] device. Information here is unofficial (and possibly incorrect) unless otherwise stated. Corrections and clarifications from Openmoko employees would be greatly appreciated.<br />
<br />
Also please '''DON'T PANIC''' when reading this page. Please give Openmoko employees time to investigate these issues and to develop a solution. Some of the items may turn out to be non-issues, or may have software workarounds. The FreeRunner's software is still under heavily development and can help fix most of this problems.<br />
<br />
=== Active Issues ===<br />
<br />
==== Poor Audio Quality ====<br />
<br />
Issue: The person on the other end of a GSM phone call may experience poor audio quality, to the point where he/she cannot carry on a normal conversation.<br />
<br />
There are three related aspects to this issue:<br />
* Call is too quiet (mixer settings for mic and/or earpiece are set too low)<br />
* Caller hears a loud echo of their own voice [http://docs.openmoko.org/trac/ticket/1267 #1267]<br />
* Buzzing noise caused by GSM radio interference [http://docs.openmoko.org/trac/ticket/883 #883] [http://docs.openmoko.org/trac/ticket/1352 #1352]<br />
<br />
Affects: all devices but only some users (depending on many factors)<br />
<br />
Status: Under investigation. There is a possibility that the quality can be made "good enough" through software (mixer settings).<br />
<br />
The source of the GSM buzz has been [http://lists.openmoko.org/pipermail/hardware/2008-August/000415.html identified].<br />
<br />
Some [http://lists.openmoko.org/pipermail/hardware/2008-August/000451.html hidden Calypso commands] may help with the echo problem.<br />
<br />
Workarounds: Using a bluetooth headset is a possibility. <br />
<br />
===== Better mixer settings =====<br />
<br />
One confirmed good settings are here: http://www.mail-archive.com/support@lists.openmoko.org/msg00564.html<br />
Please change accordingly in /usr/share/openmoko/scenarios/gsmhandset.state. Should eliminate/lessen echo and buzz problems.<br />
<br />
==== PMU/Charger Issue ====<br />
<br />
Issue: The device may fail to boot or charge the battery if the battery is deeply discharged (far enough that its internal protection circuitry is activated). See for example this thread on the [http://lists.openmoko.org/pipermail/openmoko-kernel/2008-June/003326.html kernel list].<br />
<br />
If the battery's terminal voltage is low but greater than zero then the Neo1973 recovery method may work: Disconnect USB, remove the battery, wait 10 seconds, re-insert the battery, re-connect USB, let it charge for 1 hour (or more) without pressing any buttons.<br />
<br />
Affects: Unknown. Some discussions on the mailing list may refer to pre-production devices. <br />
<br />
Status: Fixed(?) with [http://lists.openmoko.org/pipermail/openmoko-kernel/2008-July/003799.html Werner Almesberger patches] - [http://lists.openmoko.org/pipermail/commitlog/2008-July/005403.html more here] [http://lists.openmoko.org/pipermail/community/2008-July/023392.html additional information]<br />
<br />
Workarounds: See http://lists.openmoko.org/pipermail/community/2008-July/021556.html<br />
<br />
==== Some SIMs Don't Work ====<br />
<br />
Issue: There are reports that some users cannot register with their GSM network when using certain SIM cards. See for example http://lists.openmoko.org/pipermail/community/2008-July/020370.html<br />
<br />
It is possible that there is more than one issue involved here. The observed problems ''might'' (i.e. some items are only speculation at this point) be caused by: <br />
<br />
* User error, not inserting the SIM in the correct orientation or not sliding the holder to the 'locked' position<br />
<br />
* Software issues that result in a locked SIM (not properly prompting the user for a PIN and then passing this to the SIM)<br />
<br />
* Mechanical issues with the SIM holder that prevent the pins from making reliable contact with the pads on the SIM. Note that only 6 of the 8 pins are used, and the remaining two are not connected.<br />
<br />
* Electrical incompatibility (some tests show problems with 1.8V SIMs while 2.9V ones work OK)<br />
<br />
* Firmware bugs in the TI Calypso GSM chipset. Note that one issue in this category was found and fixed on the GTA01 devices (#666 in Trac), and that specific problem should not affect the FreeRunner.<br />
<br />
* Defective SIMs, i.e. ones that do not comply with the applicable standards and are acknowledged as being defective by the carrier (even if they happen to work in some phones). <br />
<br />
* You may have true 3G operating at 2100 and your sim doesn't fallback to GSM. The Phone works on 850/1800/1900 or 900/1800/1900.<br />
<br />
See also: <br />
* http://wiki.openmoko.org/wiki/Carriers/ATT<br />
* http://wiki.openmoko.org/wiki/Carriers/Rogers<br />
<br />
Affects: Only a subset of users (details unknown).<br />
<br />
Status: Under investigation. Please add your information to [[FreeRunner_unable_to_work_with_3G_SIM_cards]] or [[GSM network registration]]<br />
<br />
Workarounds: It may be possible to obtain a different model of SIM from your GSM carrier.<br />
<br />
=== Known/Accepted Issues ===<br />
<br />
This section lists items that are acknowledged as being less than ideal, but are considered to be acceptable in the shipping product. They will not be discussed in detail on this page.<br />
<br />
* Poor performance + slow bus speed of the Glamo GPU - discussed to death on the mailing lists and IRC. <br />
* [http://lists.openmoko.org/pipermail/hardware/2008-April/000055.html GPS antenna switch] driven out-of-spec - does not appear to have a significant effect on device performance<br />
* Poor low-frequency audio response with low-impedance headphones, e.g. as discussed in this thread: http://lists.openmoko.org/pipermail/openmoko-kernel/2008-March/001999.html (NOTE - this thread refers to pre-mass-production devices)<br />
** Can be fixed to an semi-acceptable level (if not high fidelity most probably) by adjusting "Bass Volume" to full (15) and "Bass Filter" to "100Hz @ 8kHz" (bass will be boosted <= 600Hz when playing back at 48kHz) or "200Hz @ 8kHz" (<= 1200Hz @ 48kHz). The default is 130Hz @ 48kHz and does not help much with the more wider scope of low frequencies.<br />
** Ideally someone would record output and find out which setting produces best output, ie. compensating for the loss of low frequencies without boosting too high frequencies with this "bass" boost.<br />
<br />
=== Resolved Issues ===<br />
<br />
These are issues that have been discussed in the past, but have been fixed (or turned out not to be a problem) for the mass-produced devices.<br />
<br />
* Excessive LED current - Some early units lacked a current-limiting resistor for the LEDs. This has been fixed for the production units.<br />
* Battery life - At this time it appears that the FreeRunner battery life will be acceptable once suspend/resume support has been implemented in software.<br />
* slow GPS TTFF - see [[GPS Problems]]<br />
==== Empty NOR Flash ====<br />
<br />
Issue: NOR flash (backup copy of u-boot) is not programmed. [http://docs.openmoko.org/trac/ticket/1568 #1568]<br />
<br />
Affects: Unknown - maybe only 1 or 2 devices? Also need to confirm that the bug report was from a mass-production unit rather than an earlier prototype.<br />
<br />
Status: Solved. The new devices are tested better if they have the NOR flashed programmed and aren't shipped if the test fail.<br />
<br />
Workarounds: Use the NAND copy of u-boot and be careful not to brick the device unless a debug-board is available.<br />
<br />
<br />
==== Debug board has wrong vendor/product ID ====<br />
<br />
Issue: A debug board is not reporting the expected USB Vendor/Product ID.<br />
<br />
Affects: Only [http://lists.openmoko.org/pipermail/device-owners/2008-July/001775.html one report] has been seen so far.<br />
<br />
Status: Probably a single case scenario.<br />
<br />
Workarounds: Edit configuration files (e.g. openocd.conf) to use the IDs that the board is reporting.<br />
<br />
== List of "Current issues" Imported from the "Community update page" ==<br />
(to be sorted)<br />
<br />
The information below has been collected from various sources, feel free to add questions and comments here.<br />
<br />
===GPS Performance of the FreeRunner===<br />
The poor GPS performance on the FreeRunner has been traced to an<br />
interaction between the microSD card and the GPS unit. A software<br />
and a hardware fixes are available, see [[GPS Problems]].<br />
<br />
===GTA02 battery status===<br />
While writing a device driver for the new battery which provides an accurate counter of the charge state of the [[GTA02]], the driver developer discovered that the device driver does not get a reading of the charge state due to a very long response time with only one I/O signal when trying to read the charge state. To be able to read the battery status properly, it has been written that it will be necessary to re-design that part of the GTA02 for hardware version GTA02A5 to use two I/O signals to reduce the response time (one for transmitting commands, one for receiving data?). This was fixed two months ago (see [http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=957#c1 Bug 957]).<br />
<br />
===Delivery of a GSM firmware update for the 3G SIM bug ([http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=666 #666])===<br />
<br />
A bug in the GSM firmware prevents some USA 3G SIM cards from working properly. The bug has been fixed, but the GSM module is under extremely tight legal protection. We've been informed that everything legal has been agreed upon by all parties regarding the process that would allow you to upgrade your own GSM firmware. All that remains is to get everything signed. Apparently the process of getting things signed takes a few weeks! Meanwhile, we have resolved the difficulties I was having performing the upgrade, and I am now able to upgrade your handsets. Anyone interested in having me do this should contact me at michael@openmoko.org.<br />
<br />
=== SMedia 3362 Documentation & OpenGL ES Drivers ===<br />
There is an open source kdrive driver being written for the GTA02 which will use hardware to accelerate the XRender extension. While the chip is capable of 3D graphics, no OpenGL ES driver/library is avaliable and Openmoko developers will not be writing one in the near future (although they have not ruled it out in the long-term). <br />
<br />
Documentation for the SMedia 3362 has been promised ([http://lists.openmoko.org/pipermail/community/2007-September/010175.html see this post]). However, this refers to documentation Openmoko developers will be writing themselves, not the technical documentation SMedia have provided Openmoko with. The Openmoko developers had to sign an NDA with SMedia to obtain this documentation and are therefore unable to pass this information on to community developers. (See [http://lists.openmoko.org/pipermail/community/2007-November/011349.html this post] for details)<br />
<br />
=== Power Management on the Neo1973/FreeRunner===<br />
The current battery life of the Neo1973 and FreeRunner is not satisfactory. A lot of changes seem to be necessary to the kernel, drivers and related user-space applications. Hopefully the situation will improve over time.<br />
<br />
[[Category:Neo FreeRunner Hardware]]</div>DolfjeBot1http://openmoko.org/wiki/Neo_FreeRunner_HardwareNeo FreeRunner Hardware2008-08-31T12:48:51Z<p>DolfjeBot1: Replacing 'Freerunner' with 'FreeRunner'</p>
<hr />
<div>{{Languages|Neo FreeRunner GTA02 Hardware}}<br />
__NOTOC__<br />
<br />
{{gta02menu}}<br />
<br />
<gallery><br />
Image:Gta02a5 pcba cs.JPG|component (back) side NOTE: GTA02 A5 PCBA Component Side photo<br />
Image:Gta02a5 pcba ps.JPG|display (top) side NOTE: GTA02 A5 PCBA Print Side photo<br />
Image:GTA02 A5 PCB CS.jpg|component (back) side NOTE: GTA02 A5 PCB Component Side photo<br />
Image:GTA02 A5 PCB PS.jpg|display (top) side NOTE: GTA02 A5 PCB Print Side photo<br />
Image:SimpleComponentDiagram.jpg|Simplified Hardware Component Diagram<br />
</gallery><br />
<br />
<br />
[[Openmoko]] is a software distribution stack that sits on top of a [[hardware]] platform. The [[Neo FreeRunner]] phone is the second hardware platform to take advantage of Openmoko. You can find specifications of the hardware by reviewing this introduction page and the pages in the category as shown at the bottom of this page.<br />
<br />
<!-- {{note|This page is about hardware that is currently in '''design/prototype''' phase, changes are frequent}} --><br />
<br />
<br />
<br />
=Summary=<br />
Openmoko, Inc. is building a Linux based smart phone with full GPL compatible firmware source code for Openmoko, project code named GTA02 (Neo FreeRunner).<br />
<br />
Detailed hardware component selection can be found below.<br />
<br />
=Features=<br />
*Display- Topply o2.8, 480 x 640 pixels, VGA, 200 NIT minimum, resistance type touch <br />
<br />
*User Interface Navigation- Touch screen on LCD, 2 control “buttons”, 1 Power button, 1 Aux for 911 emergency call <br />
<br />
*Built-in 802.11b/g Radio (Atheros chipset AR6001 Flash version) <br />
<br />
*Built-in Bluetooth 2.0 + EDR (CSR and support PCM audio , BC4 frimware version) <br />
<br />
*Built-in 2D/3D graphics acceleration chip (S-Media 3362) <br />
<br />
*2 built-in Tri-Axis sensors (ST accelerometer LIS302DL) <br />
<br />
*Built in GPS Radio – -130 dBm with internal antenna, -157 dBm tracking on chipset specification, TTFF under 40 seconds with -130 dBm signal strength, and tracking (u-Blox) <br />
<br />
*Antenna – Specialized antenna for best in hand hold GPS, GPRS and Wi-Fi/Bluetooth performance are required, -105dBm on receiving, Tx 30dbm+2 on GSM <br />
<br />
*External Antennae – MMCX GPS connector <br />
<br />
*GPRS Radio –GSM/GPRS radio. A Pre-PTCRB certified module will be preferred <br />
<br />
*Linux – Linux kernel 2.6.24 or later Openmoko kernel <br />
<br />
*USB - Client and Host mode switch-able (to be used for software downloading), provide host 5V power <br />
<br />
*Power- Normal mode power will be via 1200 mAh battery with built-in coulomb counter, could charge via specialized charger. Internal Lithium Ion or Lithium Polymer battery will keep device in standby mode. Battery life (Approximation/Ideal Target) Standby time 150-200 Hrs (GSM) Talk time (Backlight off) Up to 3-4 hrs(GSM) <br />
<br />
*LED- LED indicator under Aux/Power button key<br />
<br />
=Hardware Specification=<br />
===Hardware Electrical=== <br />
<br />
*400/500 MHz Samsung 2442B Processor/SOC (400 minimum, ARM920T core, ARMv4T)<br />
*Boot code in NAND FLASH or 2MB NOR FLASH (optional design)<br />
*128 MB SDRAM total, 64 MB CPU internal, 64 MB external <br />
*256MB NAND Flash MCP package. <br />
<br />
=== Display === <br />
*Topploy VGA ; 2.8” diagonal, 480 x 640 pixels, 16 bit color depth<br />
*Transmissive display: good readability in high ambient light is essential <br />
*White LED backlight. Required brightness is 200 NIT minimum. <br />
*Resistance type touch panel.<br />
<br />
=== WiFi 802.11 b/g transceiver === <br />
*Must have GPL support source or GPL compatible policy<br />
*TX power at 11 Mbps: 13 dBm minimum <br />
*RX sensitivity at 11 Mbps: -89 dBm desired, -83 dBm minimum <br />
*AP mode desirable, not required <br />
*WEP and WPA supported <br />
*Atheros preferred because it's GPL policy<br />
<br />
=== Serial interfaces (UART) ===<br />
*Three serial interfaces are required <br />
*Console <br />
*A-GPS or GPS<br />
*GSM/GPRS<br />
<br />
=== Accelerometer ===<br />
* 2x accelerometer required<br />
* Could support interrupt while suspend or power save mode<br />
* 3 axis sensing<br />
<br />
=== A-GPS === <br />
*GPS chipset receiver and antenna <br />
*Sensitivity at Antenna port: -157 dBm tracking on chipset specification<br />
*LNA and SAW filter for maximum interference protection<br />
*Cold start time to first fix: 40 sec typical at -130 dBm, 60 sec max<br />
*Must support GPL for Assist-GPS function with open API<br />
*Industry quality GPS <br />
*Could fit in GTA01 GPS area on the PCB<br />
<br />
=== GPS Antenna Performance === <br />
*Antenna is passive and internal; 15 mm x 15 mm ceramic patch is nominal design <br />
*Antenna LNA and SAW filter are required to meet GPS performance <br />
*15 mm square ground plane (minimum 1 mm ground border around patch) (TBA) <br />
*There will be one external GPS antenna connector (MMCX)<br />
*C/N ratio should higher than 35 on production testing<br />
<br />
=== Buttons === <br />
*Touch screen over LCD is primary data entry mechanism <br />
*Two “hard” buttons: Power button (on side of Neo1973) is a mechanical switch actuated by a plastic pushbutton in a hole in the housing. Aux (911) button on the top of the device, All two of these buttons, when pushed by the operator, are binary inputs (on/off or pressed/not pressed) to the software. The effect of each button is determined by the application software in the device <br />
*Buttons may need to be backlit<br />
*50000 cycles on hardware specification <br />
<br />
=== Sound outputs === <br />
*Speaker in box (need good volume and acoustic behavior in noisy environments)<br />
*Audio is monophonic*Max volume: 100 dB at 5 cm to assure good performance in environment.<br />
*Support earphone with mic by jack<br />
<br />
=== Power Design Requirements===<br />
*Software based power management unit preferred<br />
*NXP PCF series preferred<br />
*Need support charge from USB function<br />
*Need support powered by USB function<br />
*Power switch: Neo1973 will have a power switch, for power on/off and suspend <br />
* Power/Aux switch must be backlit <br />
*Switch controls whether device is running or suspended by presses of the switch <br />
*Switch does not shut off the power; it only suspends/resumes the device <br />
*Internal Li-Ion or Li-Polymer battery is included. This battery supplies standby power to the device eliminates the rebooting of the device when local power is again reapplied. Battery is 1200 ma-hr. <br />
*Battery life (Approximation) Ideal/Target Standby time 150-200 Hrs (GSM) Talk time (Backlight off) Up to 4 hrs(GSM) <br />
*Estimated current draw for the entire device when in suspend mode (and ALL peripherals are turned off or set for deep sleep) is <5 mA at 3.6 volts (Li-Ion terminal voltage).<br />
*GSM module deep sleep(alive and keep contact with base station) stage should take less than 8mA<br />
*Battery will reach half capacity (~600 mAh) with 500 charge-discharge cycles. This will occur in less than 2 years of daily service. <br />
*When powered continuously, Neo1973 must suspend (to low power mode) based either on observed low battery voltage condition or a configurable time delay. <br />
*Neo1973 must monitor battery status while suspended and resume automatically if the charger is inserted. <br />
*Primary power connection: 1200mAh battery <br />
*USB charger have ID pin 47.5k pull down for Openmoko identification <br />
*Indicators: an LED indicator visible from the side of the unit will illuminate when charging or have missing incoming call<br />
<br />
=== GSM/GPRS ===<br />
*850/1800/1900 and 900/1800/1900 MHz bands must be supported <br />
*Design should allow for multi-band version (850/900 MHz) <br />
*Module based GPRS transceiver could meeting PTCRB and appropriate FCC certifications. It preferred that the module be pre-certified with PTCRB or OTA test <br />
*FCC/CE certification required for GSM/GPRS part <br />
<br />
=== GSM-GPRS Antenna Performance === <br />
*-105 dBm receiving on each channel (GSM/PCS) <br />
*30+2 dBm transmission on GSM channel <br />
<br />
=== Wi-Fi Modules ===<br />
*Must support GPL driver<br />
*Atheros AR6k preferred<br />
*Flash version required<br />
<br />
=== Wi-Fi Antenna Performance === <br />
*The Wi-Fi antenna with TX 13 to 15 dBm<br />
*RX -89 to -83 dBm @802.11b 11Mbps or an equivalent performance antenna <br />
<br />
=== Bluetooth ===<br />
*CSR BC4 or later solutions<br />
<br />
=== USB === <br />
*Neo FreeRunner GTA02 will have USB, client/host. Using USB 1.1 <br />
*Provides USB host 5v power<br />
*Could be powered by USB<br />
<br />
=== Microphone === <br />
1 microphone is in the device <br />
<br />
=== Firmware Image ===<br />
*Using Linux 2.6.24 or later<br />
*Could support boot from NAND or Boot from NOR<br />
*Shipping image should come with basic phone function<br />
*Could do full firmware upgrade by USB cable<br />
<br />
=== PSN ===<br />
*Device will have a PSN (product serial number) printed on the product label and machine readable in system NAND memory<br />
<br />
=== IMEI ===<br />
*Production phase should have IMEI code written<br />
<br />
= Package Specification = <br />
*Weight: ~133 grams with battery. <br />
*4 in 1 laser pen passed RoHs and safty regulation for laser equipment safty<br />
*1x 512MB microSD Card (SanDisk/Transcend)<br />
*1x USB cable Standard A to mini-B connector<br />
*1x 1200mAh smart/gauge battery<br />
*Quick start guide <br />
*5v USB power cord w/100-240 switchable power plug <br />
*Safety card, warranty card<br />
*Package could pass 1m to 1.5m drop test<br />
*AC USB charger,100v-240v, Passed UL and all required safety regulation<br />
*Must pass FCC/CE certification<br />
*Must pass NCC certification for Taiwan import regulation<br />
*RoHS Compatible<br />
*WEEE Report required<br />
<br />
= Life Cycle Specification = <br />
<br />
=== Product Life === <br />
The product is designed to last a minimum of 2 years. <br />
<br />
=== Operating Temperature === <br />
*Target operating range is –10°C to +60°C <br />
<br />
=== Storage Temperature === <br />
*-15 deg C to +70 deg C <br />
<br />
=== ESD === <br />
The device can withstand a 4.0kV contact discharge and 8.0kV air <br />
<br />
=== Drop test ===<br />
Should pass 1m direct drop to concrete ground or 1.5m on slide with carpet<br />
<br />
<br />
= GTA02 Hardware Component Selection =<br />
<br />
== Physical Dimensions ==<br />
* 120.7 x 62 x 18.5 mm (4.75 x 2.44 x 0.728 inch)<br />
* 110 +/- 5 g (4 ounces) without battery <br><br />
<br />
== Main components ==<br />
=== Processor ===<br />
The main Processor (CPU) of the Neo1973 GTA02 is a [[Samsung S3C2442B B54]] (running at 400 MHz)<br />
<br />
* Product Homepage: [http://www.samsung.com/global/business/semiconductor/productInfo.do?fmly_id=229&partnum=SC32442 Samsung SC32442B]<br />
* User Manual: [http://210.118.57.197/Products/Semiconductor/MobileSoC/ApplicationProcessor/ARM9Series/SC32442/um_s3c2442b_rev12.pdf Samsung SC32442B]<br />
* Core: ARM920T<br />
* Instruction Set: ARMv4<br />
* Built-in 64MB SDRAM<br />
* Built-in 256 MB NAND<br />
* GPIO Assignments: https://svn.openmoko.org/trunk/doc/hardware/GTA02v4/gpio.txt<br><br />
* Evaluation board: [http://www.meritech.co.kr/products/product_view.php?num=52 S3C2442 EVB]<br />
<br />
=== Power Management ===<br />
A NXP PCF50633 04 N3 is used for [[Neo1973_Power_Management|power management]].<br />
<br />
* NXP PMU index: [http://www.nxp.com/products/power_management/pmu/index.html NXP PMU index page]<br><br />
* Product Datasheet: [http://people.openmoko.org/tony_tu/GTA02/datasheet/PMU/PCF50633DS_02.pdf NXP PCF50633 Product Data Sheet]<br><br />
* Product User manual: [http://people.openmoko.org/tony_tu/GTA02/datasheet/PMU/PCF50633UM_6.pdf NXP PCF50633 User Manual]<br><br />
**Special thanks NXP provide full user manual and support openness for all developer<br />
**Datasheet/User manual usage [http://lists.openmoko.org/pipermail/community/2008-March/013898.html was legally authorized by NXP]<br />
* Connected to: S3C2442 via I2C, client address is 0x08. <br><br />
* Driver Source: https://svn.openmoko.org/trunk/src/target/kernel/patches/pcf50633.patch<br><br />
<br />
=== Flash ===<br />
==== NAND Flash ====<br />
256MB integrated Samsung NAND flash inside the 2442 multi-chip package, attached to the S3C2442 NAND controller<br />
<br />
* Product Homepage: [http://www.samsung.com/global/business/semiconductor/productInfo.do?fmly_id=229&partnum=SC32442 S3C2442]<br />
* Data Sheet: S3C2442 B54 comes with 256 MB NAND MCP package<br />
* Connected to: S3C2442 NAND controller<br><br />
<br />
==== NOR Flash ====<br />
<br />
16MBit ST M58WR016KB706E NOR flash for 'unbrickable emergency boot' feature.<br />
<br />
* Product Homepage: [http://www.st.com/stonline/products/families/memories/fl_nor_mob/index.htm ST Mobile Flash NOR/Mobile Terminal]<br />
* Data Sheet: [http://www.st.com/stonline/products/literature/ds/13023/m58wr032qb.pdf M58WR016]<br />
* Connected to: S3C2442 NAND controller<br><br />
<br />
=== SDRAM ===<br />
128MB SDRAM (64MB inside 2442 MCP, 1x Samsung K4M51323PC) attached to S3C2442 SDRAM controller<br />
* Product Homepage: [http://www.samsung.com/global/business/semiconductor/productInfo.do?fmly_id=136&partnum=K4M51323PC Samsung K4M51323PC]<br />
* Data Sheet: [http://www.samsung.com/global/system/business/semiconductor/product/2007/6/11/MobileSDRAM/MobileSDRSDRAM/512Mbit/K4M51323PC/ds_k4m51323pc.pdf Samsung K4M51323PC]<br />
* Connected to: S3C2442 <br><br />
<br />
== GSM/GPRS ==<br />
The [[GSM]] (including GPRS) modem is Texas Instruments Calypso based.<br />
<br />
* Connected to: S3C2442 UART1 (full-uart, RxD, TxD, CTS, RTS), /dev/ttySAC0 in userspace<br />
* PM Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/gta01-power_control.patch<br />
* Accessible GSM/GPRS antenna jack (if battery cover is removed)<br><br />
<br />
=== CALYPSO ASIC digital baseband ===<br />
Unfortunately we cannot provide many details on the GSM chipset due to very tight [http://en.wikipedia.org/wiki/Non-disclosure_agreement NDA]s. However, this is not neccessarily required, since it interfaces using a standard UART serial line with the S3C2442. On that interface, [http://www.3gpp.org/ftp/Specs/archive/07_series/07.05/ GSM 07.05], [http://www.3gpp.org/ftp/Specs/archive/07_series/07.10/ GSM 07.10] and other standardized protocols are used.<br />
<br />
The NDAd documentation for the calypso, [http://cryptome.org/ti-calypso1.pdf register definition ] and [http://cryptome.org/ti-calypso2.pdf hardware definition ] was leaked onto a public forum on the 4th of March by persons or persons unknown.<br />
The legality of reading these files may vary according to your local laws, as may generating code from them.<br />
<br />
<br />
*Calypso D751992AZHH<br><br />
*The firmware within GTA02 should be moko6 or later (internal code name)<br />
<br />
=== TI TWL3025BZGMR analog baseband ===<br />
*Product Homepage: [http://focus.ti.com/general/docs/wtbu/wtbuproductcontent.tsp?templateId=6123&navigationId=12295&contentId=4703 TWL3014]<br><br />
<br />
=== TI TRF6151 (GSM/PCS) RF Transceiver ===<br />
*Product Homepage: [http://focus.ti.com/general/docs/wtbu/wtbuproductcontent.tsp?templateId=6123&navigationId=12296&contentId=4701 TRF6151] <br><br />
GPRS Class12/CS4 <br><br />
<br />
== AGPS ==<br />
u-blox ANTARIS 4 chip<br />
* Connected to: S3C2442 UART2, /dev/ttySAC1 in userspace<br />
* Driver: none needed, talks standard NMEA<br />
* u-blox Antaris 4 Protocol [http://www.u-blox.com/customersupport/antaris_doc.html Protocol download page]<br />
* ATR0635 Datasheet: [http://www.u-blox.com/products/Data_Sheets/ATR0630_35_SglChip_Data_Sheet(GPS.G4-X-06009).pdf u-blox ATR0635]<br><br />
<br />
== Accelerometers ==<br />
Two ST LIS302DL<br />
* Homepage: http://www.st.com/stonline/products/literature/ds/12726/lis302dl.htm<br />
* Datasheet: http://www.st.com/stonline/products/literature/ds/12726.pdf<br />
* Connected to: S3C2442 via SPI interface<br />
* S3C2442 SPI EINT interrupt inputs<br><br />
<br />
== Graphics/3D Acceleration ==<br />
<br />
Smedia Glamo 3362.<br />
* Homepage: http://www.smediatech.com/product3362.htm<br />
* Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/smedia-glamo.patch<br />
* Data sheet: This is not available, as it is under NDA. It will likely never be available. (Source: Raster - IRC). There is hope that the glamo chip features may be usable even without a NDA, see [http://unadventure.wordpress.com/2008/06/08/accelerating-in-my-pocket/ the hack here]<br />
* Connected to: S3C2442 Address/Data bus <br><br />
<br />
=== microSD ===<br />
The GTA02 has one microSD aka Transflash slot. Using the Glamo 3362 MMC/SD controller<br />
<br />
*It should support SDHC, and 4GB card has been tested. Anyone with 8GB card? MicroSD slot is [[Disassembling_Neo1973#Opening_back_cover|under battery]].<br />
* Connected to: Glamo 3362 MMC/SD controller<br />
* Driver: Check svn for the SMedia driver with SD implementation<br />
* [[Supported microSD cards]]<br />
* Specifications: [http://www.sdcard.org/about/memory_card/pls/ SD Simplified Specification], [http://www.mmca.org/compliance/buy_spec/AN_MMCA050419.pdf MMC (partial)], [http://www.sandisk.com/Assets/File/OEM/Manuals/manual-rs-mmcv1.0.pdf MMC (product manual)]<br />
* SANDISK 128 MB/512 MB and some 4G SDHC card been verified could work on GTA02<br><br />
<br />
== LCD Module (LCM) ==<br />
Toppoly (tpo) 2.8" diagonal (1.7" x 2.27" - 43mm x 58mm) 480x640 TD028TTEC1 module, using a Toshiba JBT6K74 TFT <br />
LCD Driver Chipset.<br><br />
* Homepage: [http://www.tpo.biz/ENG/business-eng/Activer-Matrix-VGA.htm Activer-Matrix-VGA.htm]<br />
* Specification: FIXME<br />
* Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/gta01-jbt6k74.patch<br />
* Backlight Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/gta01-backlight.patch<br />
* Connected to: Glamo3362 LCM interface and Glamo3362 SPI Interface<br><br />
<br />
==== Touch Screen ====<br />
* Connected to: S3C2442 TS controller<br />
* Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/s3c2410_touchscreen.patch<br />
<br />
== Bluetooth Module==<br />
Delta DFBM-CS320 Class2 Module, using CSR BlueCore4<br />
<br />
* Data Sheet: [http://www.delta.com.tw/product/cp/vco/BT/download/pdf/CS/2.DFBM-CS320.pdf 2.DFBM-CS320.pdf]<br />
* CSR Data Sheet: [http://www.csrsupport.com/download/2302/CS-101564-DSP10%20BlueCore4-ROM%20Product%20Data%20Sheet.pdf CS-101564-DSP10 BlueCore4-ROM Product Data Sheet.pdf]<br />
* Driver: Stock Linux Kernel BlueZ<br />
* Connected to: S3C2442 USB Host controller (OHCI)<br />
* PM Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/gta01-power_control.patch<br><br />
<br />
=== Bluetooth Audio ===<br />
This one is wired via PCM bus from the CSR Bluetooth chip to the Wolfson codec.<br><br />
<br />
== WiFi Module==<br />
<br />
Accton (WLAN 802.11b/g SiP-M WM3236AQ(Flash Ver:2.0 Atheros AR6001GZ)<br />
* Connected to: S3C2442 SDIO Host controller<br><br />
* Datasheet: [http://www.accton.com/products/Datasheet/WM3236A.AQ.pdf Accton 3236AQ datasheet]<br><br />
* Driver: http://svn.openmoko.org/developers/sameo/patches/<br><br />
<br />
== Vibrator ==<br />
* Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/gta01-vibrator.patch<br />
* Connected to: S3C2442 GPIO<br />
<br />
== USB Host ==<br />
The USB Host controller is inside the S3C2442<br />
* Driver: Stock Linux kernel ohci_hcd<br />
* USB version 1.1<br />
* Supply USB 5v in Host mode using usb power switch AAT1275IRN-5.0-T1<br />
** http://www.analogictech.com/products/digitalfiles/AAT1275.pdf<br />
* A net EN_USBHOST is controlled by PMU GPIO "GPO", this one signal when asserted (high)<br />
** enables generation of 5V for external device using a charge pump<br />
** enables connection of 15K pulldowns to D+ and D- to allow device insertion and removal detection for host mode<br />
** DISABLES the path for USB power to charge the battery<br />
<br />
It should also be possible to use host mode with externally-provided power. This will allow the FreeRunner to be connected to a USB device and be powered and charging the battery if present at the same time.<br />
<br />
* Connect 0V, d+, d-, +5 to your USB device<br />
* Connect a 15k ohm resistor between d+ and ground<br />
* Connect a 15k ohm resistor between d- and ground<br />
* Connect 0V, +5 to your >1A power source<br />
** If your power source was not the Openmoko 1A charger, additionally connect a 47K ohm 5% resistor between the ID pin and ground to pretend to be the 1A charger.<br />
<br />
In addition you need to make sure EN_USBHOST signal that enables the physical Host mode power generation and disables the USB -> PMU charging path is deasserted. This may be taken care of automatically shortly by detection of the 48K resistor on a USB insertion leading to forcing EN_USBHOST deasserted. The charge pump that generates the 5V in host mode doesn't seem to mind getting external 5V given to it, but the real issue is that the battery will not be charged at all if we leave EN_USBHOST asserted since one of its jobs is to stop that happening.<br />
<br />
== USB Device ==<br />
The USB Device controller is inside the S3C2442 <br />
* Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/s3c2410_udc.patch<br />
* Please see [[USB Product IDs]] on information about which Vendor/Product IDs we use<br />
* 1200mAh lithium battery charges when connected to powered host.<br />
* Mini-AB connector similar to [http://www.cypressindustries.com/shoponline/proddetail.asp?prod=CCMUSBAB-32005-700&cat=34 this one].<br />
<br />
== I2C Devices ==<br />
I2C is a simple communication standard intended to move small amounts of data a few inches between chips.<br />
Please see [[I2C | Neo I2C Devices]] for more information & a list of devices & the addresses currently in use & documented for the Neo1973.<br><br />
<br />
== Audio ==<br />
See also: [[Neo1973 Audio Subsystem]]<br />
<br />
=== Wolfson Codec ===<br />
There's a [[WM8753]] Wolfson Microelectronics CODEC (This is not a 'smart' codec that can interpret MP3/... it is a simple dumb 'sound card'.)<br />
* Product Homepage: http://www.wolfsonmicro.com/products/WM8753/<br />
* Data Sheet: [http://www.wolfsonmicro.com/uploads/documents/en/WM8753.pdf WM8753.pdf]<br />
* Connected to: S3C2442 IIS interface (PCM data), S3C2442 I2C (Control)<br />
* Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/asoc.patch<br />
<br />
=== Mono Amplifier ===<br />
There's a National Semiconductor [[LM4853]] Mono Amplifier at the analog audio output of the WM8753<br />
<br />
* Product Homepage: [http://www.national.com/pf/LM/LM4853.html LM4853.html]<br />
* Data Sheet: [http://www.national.com/ds.cgi/LM/LM4853.pdf LM4853.pdf]<br />
* Connects to (LM4853 pin): <br />
** S3C2442 GPIO: HP_IN, AMP_SHUT (shutdown); <br />
** Wolfson WM8753: LOUTL (LEFTIN), LOUTR (RIGHTIN); <br />
** speaker4102: (LEFTOUT/BLTOUT-, BLTOUT+);<br />
** headset-jack: ring 2 (RIGHTOUT), ring 3 (LEFTOUT/BLTOUT-) via 1uF-33R each<br />
<br />
=== Analog wired Headset ===<br />
There's a four-ring 2.5mm stereo jack which provides connectivity to old-fashioned wired headsets.<br />
<br />
The headsets used by Motorola smartphones (A780,A1200, ...) and the V-360 have a compatible configuration.<br />
<br />
ring<br><br />
1(base): GND<br><br />
2: right out<br><br />
3: left out<br><br />
4(tip): mic + HOLD-button(press:short to GND)<br />
<br />
=== Buttons ===<br />
The Neo1973 GTA02 features two buttons:<br />
* [[Neo1973 Power Button|The Power Button]]<br />
* [[Neo1973 AUX Button|The "Aux" button]]<br />
<br />
== Case ==<br />
The case for the FreeRunner is all black, as seen on the front page of the wiki.<br />
<br />
Openmoko has released the CAD files for the case schematics for the Openmoko [[Neo1973]] (GTA01) and Neo FreeRunner. These are available in the original Pro/E (.asm/.prt) format and alternative formats created from the originals.<br />
<br />
We welcome your assistance in providing other formats. If you are able to convert CAD files from Pro/E format to other formats, please contact [mailto:michael@openmoko.org]. We are especially interested in the DXF format and in images rendered from these files.<br />
<br />
* [http://downloads.openmoko.org/CAD/NeoFreeRunner_ProE.zip The original Pro/E (.asm/.prt) format]<br />
<br />
[http://downloads.openmoko.org/CAD/ Browse CAD directory]<br />
<br />
=Accessory=<br />
<br />
== Stylus ==<br />
<br />
Using 4 in 1 laser pen<br />
*Vendor: [http://www.quarton.com/laser_pen.html Quarton XPII]<br />
*GTA02 standard setup comes with [http://www.quarton.com.tw/laser_pen_infiniter_xp_2.html QUARTON XPII 4 in 1 laser pen]<br />
<br />
== Battery ==<br />
The [[Neo FreeRunner (GTA02) Battery]] is mechanically and electrically compatible with the [[Neo1973 GTA01 Battery]], as well as limited compatibility with a Nokia BL6C battery.<br />
According to [http://lists.openmoko.org/pipermail/community/2007-February/003758.html this] post on the mailinglist.<br />
[http://wiki.openmoko.org/index.php?title=Image:Neo1973-with-BL5C-battery.png Photo] of the battery inside the Neo1973.<br />
<br />
* GTA02 using the smart battery based on TI bq27000 chipset<br />
* SANYO UF653450S 1200mAh cell.<br><br />
* Battery schematics: [http://people.openmoko.org/tony_tu/GTA02/hardware/GTA02/CT-GTA02.pdf GTA02 Smart Battery Schematics]<br />
<br />
== microSD Card ==<br />
<br />
GTA02 should come with one of following microSD card<br />
<br />
* [http://www.transcendusa.com/ Transcend] 512MB microSD card<br />
* [http://www.sandisk.com/ SanDisk] 512MB microSD card<br><br />
<br />
== Charger ==<br />
<br />
AKII Technology Charger<br />
<br />
*Model: [http://www.ak2.com.tw/pd_main.asp?sg_id=11 A10P1-05MP]<br />
*Input: 100-240v~ /0.3A<br />
*Output: +5v up to 2.0A<br />
*Add 47.5k 1% resistor between ID pin and ground for openmoko charger identification<br><br />
<br />
= History =<br />
<br />
== GTA02v1 ==<br />
First generation of prototypes that was given to internal Openmoko software developers. Total 30 pcs fabricated.<br />
<br />
*It is working just fine, but still based on 2440, with external NAND/SDRAM and no NOR flash<br />
*Using the PCF50633 05 N3 due to 04 N3 not available, re-work power for basic schematics verification<br />
*Using GTA01 SIM socket<br />
*Add external debug port<br />
*Still using Global locate A-GPS<br />
* ATAG_REVISION: 0310<br />
<br />
== GTA02v2 ==<br />
Second generation of prototypes, Total 50 pcs run at Taipei SMT factory MOUNT<br />
<br />
*Ideal is have 256 MB NAND on Samsung package, Due to chip availability Start using S3C2442 B43<br />
*Using correct PMU PCF50633 04 N3<br />
*Change new SIM socket<br />
*Change to u-blox A-GPS<br />
*Change LCM power from 3.3v to 1.8v<br />
*USB power switch layout/pin assignment mistake, could not verify USB host supply 5v function<br />
*GPS function verified ok with good sensitivity<br />
* ATAG_REVISION: 0320<br />
<br />
== GTA02v3 ==<br />
Production verification version, 2007/10/11 28 pcs fabricate at FIC SuZhou<br />
<br />
*Still using S3C2442 B43 for hardware verification<br />
*Using control pilot run to verify S3C2442 B54 chips<br><br />
* ATAG_REVISION: 0330<br />
<br />
== GTA02v4 ==<br />
Mass production release candidate version 1<br />
<br />
2 weeks after v3 gerber out, release the v4 gerber, and 2007/10/20 20 pcs fabricate at FIC SuZhou <br />
<br />
*Change LCM power from 1.8v to 3.3v for display stability issue<br />
*fabricate another 200 pcs for yield rate/production verification<br />
*fabricate 50 pcs with S3C2442 B43 (128 MB NAND) for quality comparsion<br />
*USB host power chip have some output voltage stability issues with Vb/Vcc comes from different power source, need layout change to fix the issue<br />
*Battery Coulomb design not working on A4<br />
* ATAG_REVISION: 0340<br />
<br />
== GTA02v5 ==<br />
Mass production candidate version 2/Mass production version<br />
<br />
* First batch fabricate 2008/1/14 at FIC SuZhou<br />
* Mass production A5 trial run start from 2008 March, including some resistor/capacitor change compare with inital 100 pcs prototypes A5, and prototypes for GTA02 developers was tracked in the [[Prototypes| Prototypes Page]]<br />
* Coulomb counter issue fixed<br />
* USB host power switch fixed<br />
* Need add capacitor for PMU Vbat input for stability issue, this could be done by direct SMT or hand rework<br />
* Need rework (still using SMT in production) add capacitor for PMU Vbat input for PMU stability issue.<br />
* Need manual rework GSM IR UART path a 100k pull down for better GSM deep sleep<br />
* ATAG_REVISION: 0350<br />
<br />
===GTA02 mass Production version change list===<br />
*PMU's LED power error: PMU potential damage issue<br />
*NOR FLASH enable WP: User can write data into NOR FLASH.<br />
*CE CS/RS fine tune: Audio's background noise too high<br />
*I2C pull high resistor: The resistor is too high and signal is distorted <br />
*GSM leakage current: TX_MODEM has a pull high resistor on IO_3V3<br />
*Power consumption: Disable keep active function<br />
*SDIO clock and esd protect resistor<br />
*Refer to Datasheet: R1526 to 33K<br />
*GSM modem on pin: The R1018 is too small and has some leakage current<br />
*LED driving transistor: When GPIO is on, the transistor will be draw more current on LED. This is component change fix, do not need change PCB or re-work.<br />
<br />
== GTA02v6 ==<br />
Mass production candidate version 3/Mass production version<br><br />
<br />
A6 will be fine tune version of A5, only minor schematic change for better product quality and version control. Capacitor and resistor change A6 also on mass production A5<br><br />
<br />
*First 100 pcs start from 2008 mid April, and factory make component placement mistake on GSM, second 100 pcs PCB arrive time TBD. <br />
*Add capacitor space for Vbat, reduce the SMT effort<br />
*Add GSM IR resistor for better GSM deep sleep<br />
*Reserve 3 GPIO for hardware version control<br />
*Fixed LEDs power usage (from about 150mW of v5 to about 25mW)<br />
* ATAG_REVISION: 0360<br />
<br />
=== GTA02 A5 to A6 changes ===<br />
*Power Glitch on VB_SYS: Add capacitor on layout, Mass production A5 also apply this change.<br />
*G-sensor separate these interrupt pins: At A5, each accelerometer INT1/INT2 connected to same line, at A6 only INT1 was connected.<br />
*GSM_modem power source Reduce power's ripple when the phone is talking<br />
*Keep active Disable keep active function, just fine tune<br />
*GPIO for version control <br />
*GSM RX_IR has some noise Add resistor and reduce GSM RX_IR noise and gsm can't enter suspend mode easily, apply on mass production A5.<br />
*LED driving transistor apply on mass production A5.<br />
*LCM's VDDIO We can totally power off LCM's power, save about extra 1mA.<br />
<br />
= Debug Board =<br />
<br />
== Debug Board Connector definition ==<br />
<br />
This is the connector used to connect the [[Debug Board]] and possibly other hardware.<br />
<br />
Connections are:<br />
* 39 - GND<br />
* 38 - STDI<br />
* 37 - _RESET<br />
* 36 - STMS<br />
* 35 - STCK<br />
* 34 - STDO<br />
* 33 - GSM_EN<br />
* 29 - _STRST<br />
* 19 - X_I2C_SCL (H-TP4703)<br />
* 18 - X_I2C_SDA (H-TP4704)<br />
* 17 - SPI_CLK0<br />
* 16 - SPI_MOSI0<br />
* 15 - SPI-MISO0 <br />
* 14 - SS0<br />
* 13 - EINT3 (H-TP4705)<br />
* 3 - CONSOLE_TXD (H-TP4701)<br />
* 2 - CONSOLE_RXD (H-TP4702)<br />
<br />
Information from [http://people.openmoko.org/roh/Debugport_GTA01bv4.png].<br />
<br />
= Distinguishing hardware revisions =<br />
== Inside the [[Bootloader]] ==<br />
Every hardware revision has its own u-boot image type. Thus, the bootloader has the revision hard-coded.<br />
The hardware revision is passed on to the kernel via the ATAG mechanism (ATAG_REVISION)<br />
<br />
== Inside the [[Kernel]] ==<br />
The kernel receives the ATAG_REVISION during bootup, and saves its contents in the "system_rev" global variable.<br />
<br />
== From Userspace ==<br />
The kernel exports the system_rev variable in /proc/cpuinfo as "Revision :" line.<br />
<br />
= Certification =<br />
<br />
== FCC ==<br />
*For US Import<br />
** 850/1800/1900 Band, FCC ID: EUNGTA02<br />
** 900/1800/1900 Band, FCC ID: EUNGTA02E<br />
** [http://people.openmoko.org/tony_tu/GTA02/certificate/EUNGTA02_850_1800_1900/ FCC test report(GTA02)]<br />
** [http://people.openmoko.org/tony_tu/GTA02/certificate/EUNGTA02E_900_1800_1900/ FCC test report(GTA02E)]<br />
<br />
== CE ==<br />
*For Europe<br />
**Registration number: M528583V-EO<br />
**[http://people.openmoko.org/tony_tu/GTA02/certificate/CE/ CE report and certificate]<br />
<br />
== NCC ==<br />
*For Taiwan Import<br />
**NCC certification number: CCAF08DG0080T0 <br />
**[http://people.openmoko.org/tony_tu/GTA02/certificate/NCC NCC report and certificate]<br />
<br />
[[Category:GTA02 Hardware]]</div>DolfjeBot1http://openmoko.org/wiki/Neo_FreeRunner_GTA02_Hardware/ruNeo FreeRunner GTA02 Hardware/ru2008-08-31T12:48:41Z<p>DolfjeBot1: Replacing 'Freerunner' with 'FreeRunner'</p>
<hr />
<div>{{Languages|Neo FreeRunner GTA02 Hardware}}<br />
__NOTOC__<br />
__NOEDITSECTION__<br />
{{gta02menu}}<br />
Openmoko - это стек программного обеспечения, которое работает поверх [[hardware|аппаратной платформы]]. Смартфон [[Neo FreeRunner]] - это аппаратная платформа второго поколения, которая использует Openmoko. Вы можете получить сведения относительно характериск аппаратной части, просмотрев эту вводную страницу, а также другие страницы в этой категории, приведенные в нижней части этой страницы.<br />
<br />
<!-- {{note|This page is about hardware that is currently in '''design/prototype''' phase, changes are frequent}} --><br />
<br />
=Резюме=<br />
Openmoko, Inc. создает основанный на GNU/Linux смартфон применяя для Openmoko микропрограммное обеспечение с исходным кодом, полностью совместимым с условиями лицензии GPL. Кодовое имя проекта GTA02 (Neo FreeRunner).<br />
<br />
Детально аппаратные компоненты рассматриваются далее. См. также [[Neo FreeRunner GTA02 Hardware Requirements\ru]] используемые для выбора этих компонентов.<br />
<br />
<gallery><br />
Image:Gta02a5 pcba cs.JPG|нижняя сторона (сторона элементов) NOTE: Фотография стороны элементов в сборе A5 GTA02<br />
Image:Gta02a5 pcba ps.JPG|верхняя сторона (сторона дисплея) NOTE: Фотография стороны печати в сборе A5 GTA02<br />
Image:GTA02 A5 PCB CS.jpg|нижняя сторона (сторона элементов) NOTE: Фотография стороны элементов печатной платы A5 GTA02<br />
Image:GTA02 A5 PCB PS.jpg|верхняя сторона (сторона дисплея) NOTE: Фотография стороны печати печатной платы A5 GTA02<br />
Image:SimpleComponentDiagram.jpg|Упрощённая диаграма аппаратных компонентов<br />
</gallery><br />
<br />
== Расположение элементов на печатной плате ==<br />
<br />
{| class="wikitable" cellspacing="2" cellpadding="2" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #ffffff; background:#ffffff; width:100%;"<br />
! style="background:#ffffff;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #ffffff; width:33% " | <br />
<div align=center> <br />
[[Image:Gta02a5 pcba cs1.png]]<br />
</div><br />
! style="background:#ffffff;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #ffffff; width:33% " |<br />
<div align=left><br />
1. NOR Flash<br/><br />
2. SDRAM<br/><br />
3. GPS<br/><br />
4. CPU/NAND Flash<br/><br />
5. GPU<br/><br />
6. PMU<br/><br />
7. Audio Codec<br />
</div><br />
! style="background:#ffffff;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #ffffff; width:34% " |<br />
<br />
<div align="left"><br />
8. Addio Amplifier<br/><br />
9. USB Host Power<br/><br />
10. Analog Baseband<br/><br />
11. Digital Baseband<br/><br />
12. GSM SRAM/Flash<br/><br />
13. GSM RF TRanceiver<br/><br />
14. RF AMP<br />
</div><br />
|}<br />
<br />
= Аппаратные компоненты GTA02 =<br />
<br />
== Габаритные размеры ==<br />
* 120.7 x 62 x 18.5 мм (4.75 x 2.44 x 0.728 дюйма)<br />
* 110 +/- 5 г (4 унции) без батареи<br><br />
<br />
== Основные компоненты ==<br />
=== Процессор ===<br />
Центральный процессор (CPU) это [[Samsung S3C2442B B54]] (работающий на частоте 400 MHz)<br />
<br />
Назначение выводов (GPIO): https://svn.openmoko.org/trunk/doc/hardware/GTA02v4/gpio.txt<br />
<br />
<br />
<br />
=== Управление питанием ===<br />
A NXP PCF50633 04 N3 is used for [[Neo1973_Power_Management|power management]].<br />
<br />
* NXP PMU index: [http://www.nxp.com/products/power_management/pmu/index.html NXP PMU index page]<br><br />
* Product Datasheet: [http://people.openmoko.org/tony_tu/GTA02/datasheet/PMU/PCF50633DS_02.pdf NXP PCF50633 Product Data Sheet]<br><br />
* Product User manual: [http://people.openmoko.org/tony_tu/GTA02/datasheet/PMU/PCF50633UM_6.pdf NXP PCF50633 User Manual]<br><br />
**Special thanks NXP provide full user manual and support openness for all developer<br />
**Datasheet/User manual usage [http://lists.openmoko.org/pipermail/community/2008-March/013898.html was legally authorized by NXP]<br />
* Connected to: S3C2442 via I2C, client address is 0x08. <br><br />
* Driver Source: https://svn.openmoko.org/trunk/src/target/kernel/patches/pcf50633.patch<br><br />
<br />
=== Flash ===<br />
==== NAND Flash ====<br />
256MB integrated Samsung NAND flash inside the 2442 multi-chip package, attached to the S3C2442 NAND controller<br />
<br />
* Product Homepage: [http://www.samsung.com/global/business/semiconductor/productInfo.do?fmly_id=229&partnum=SC32442 S3C2442]<br />
* Data Sheet: S3C2442 B54 comes with 256 MB NAND MCP package<br />
* Connected to: S3C2442 NAND controller<br><br />
<br />
==== NOR Flash ====<br />
<br />
16MBit ST M58WR016KB706E NOR flash for 'unbrickable emergency boot' feature.<br />
<br />
* Product Homepage: [http://www.st.com/stonline/products/families/memories/fl_nor_mob/index.htm ST Mobile Flash NOR/Mobile Terminal]<br />
* Data Sheet: [http://www.st.com/stonline/products/literature/ds/13023/m58wr032qb.pdf M58WR016]<br />
* Connected to: S3C2442 NAND controller<br><br />
<br />
=== SDRAM ===<br />
128MB SDRAM (64MB inside 2442 MCP, 1x Samsung K4M51323PC) attached to S3C2442 SDRAM controller<br />
* Product Homepage: [http://www.samsung.com/global/business/semiconductor/productInfo.do?fmly_id=136&partnum=K4M51323PC Samsung K4M51323PC]<br />
* Data Sheet: [http://www.samsung.com/global/system/business/semiconductor/product/2007/6/11/MobileSDRAM/MobileSDRSDRAM/512Mbit/K4M51323PC/ds_k4m51323pc.pdf Samsung K4M51323PC]<br />
* Connected to: S3C2442 <br><br />
<br />
== GSM/GPRS ==<br />
The [[GSM]] (including GPRS) modem is Texas Instruments Calypso based.<br />
<br />
* Connected to: S3C2442 UART1 (full-uart, RxD, TxD, CTS, RTS), /dev/ttySAC0 in userspace<br />
* PM Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/gta01-power_control.patch<br />
* Accessible GSM/GPRS antenna jack (if battery cover is removed)<br><br />
<br />
=== Цифровой модулятор CALYPSO ASIC ===<br />
Unfortunately we cannot provide many details on the GSM chipset due to very tight [http://en.wikipedia.org/wiki/Non-disclosure_agreement NDA]s. However, this is not neccessarily required, since it interfaces using a standard UART serial line with the S3C2442. On that interface, [http://www.3gpp.org/ftp/Specs/archive/07_series/07.05/ GSM 07.05], [http://www.3gpp.org/ftp/Specs/archive/07_series/07.10/ GSM 07.10] and other standardized protocols are used.<br />
<br />
The NDAd documentation for the calypso, [http://cryptome.org/ti-calypso1.pdf register definition ] and [http://cryptome.org/ti-calypso2.pdf hardware definition ] was leaked onto a public forum on the 4th of March by persons or persons unknown.<br />
The legality of reading these files may vary according to your local laws, as may generating code from them.<br />
<br />
<br />
*Calypso D751992AZHH<br><br />
*The firmware within GTA02 should be moko6 or later (internal code name)<br />
<br />
=== Аналоговый модулятор TI TWL3025BZGMR ===<br />
*Product Homepage: [http://focus.ti.com/general/docs/wtbu/wtbuproductcontent.tsp?templateId=6123&navigationId=12295&contentId=4703 TWL3014]<br><br />
<br />
=== TI TRF6151 (GSM/PCS) RF трансивер ===<br />
*Product Homepage: [http://focus.ti.com/general/docs/wtbu/wtbuproductcontent.tsp?templateId=6123&navigationId=12296&contentId=4701 TRF6151] <br><br />
GPRS Class12/CS4 <br><br />
<br />
== AGPS ==<br />
u-blox ANTARIS 4 chip<br />
* Connected to: S3C2442 UART2, /dev/ttySAC1 in userspace<br />
* Driver: none needed, talks standard NMEA<br />
* u-blox Antaris 4 Protocol [http://www.u-blox.com/customersupport/antaris_doc.html Protocol download page]<br />
* ATR0635 Datasheet: [http://www.u-blox.com/products/Data_Sheets/ATR0630_35_SglChip_Data_Sheet(GPS.G4-X-06009).pdf u-blox ATR0635]<br><br />
<br />
== Акселерометры ==<br />
Two ST LIS302DL<br />
* Homepage: http://www.st.com/stonline/products/literature/ds/12726/lis302dl.htm<br />
* Datasheet: http://www.st.com/stonline/products/literature/ds/12726.pdf<br />
* Connected to: S3C2442 via SPI interface<br />
* S3C2442 SPI EINT interrupt inputs<br><br />
<br />
== Графическое/3D ускорение ==<br />
<br />
Smedia Glamo 3362.<br />
* Homepage: http://www.smediatech.com/product3362.htm<br />
* Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/smedia-glamo.patch<br />
* Data sheet: This is not available, as it is under NDA. It will likely never be available. (Source: Raster - IRC)<br />
* Connected to: S3C2442 Address/Data bus <br><br />
<br />
=== microSD ===<br />
The GTA02 has one microSD aka Transflash slot. Using the Glamo 3362 MMC/SD controller<br />
<br />
*It should support SDHC, and 4GB card has been tested. Anyone with 8GB card? MicroSD slot is [[Disassembling_Neo1973#Opening_back_cover|under battery]].<br />
* Connected to: Glamo 3362 MMC/SD controller<br />
* Driver: Check svn for the SMedia driver with SD implementation<br />
* [[Supported microSD cards]]<br />
* Specifications: [http://www.sdcard.org/about/memory_card/pls/ SD Simplified Specification], [http://www.mmca.org/compliance/buy_spec/AN_MMCA050419.pdf MMC (partial)], [http://www.sandisk.com/Assets/File/OEM/Manuals/manual-rs-mmcv1.0.pdf MMC (product manual)]<br />
* SANDISK 128 MB/512 MB and some 4G SDHC card been verified could work on GTA02<br><br />
<br />
== LCD модуль (LCM) ==<br />
Toppoly (tpo) 2.8" diagonal (1.7" x 2.27" - 43mm x 58mm) 480x640 TD028TTEC1 module, using a Toshiba JBT6K74 TFT <br />
LCD Driver Chipset.<br><br />
* Homepage: [http://www.tpo.biz/ENG/business-eng/Activer-Matrix-VGA.htm Activer-Matrix-VGA.htm]<br />
* Specification: FIXME<br />
* Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/gta01-jbt6k74.patch<br />
* Backlight Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/gta01-backlight.patch<br />
* Connected to: Glamo3362 LCM interface and Glamo3362 SPI Interface<br><br />
<br />
==== Сенсорный экран ====<br />
* Connected to: S3C2442 TS controller<br />
* Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/s3c2410_touchscreen.patch<br />
<br />
== Модуль Bluetooth ==<br />
Delta DFBM-CS320 Class2 Module, using CSR BlueCore4<br />
<br />
* Data Sheet: [http://www.delta.com.tw/product/cp/vco/BT/download/pdf/CS/2.DFBM-CS320.pdf 2.DFBM-CS320.pdf]<br />
* CSR Data Sheet: [http://www.csrsupport.com/download/2302/CS-101564-DSP10%20BlueCore4-ROM%20Product%20Data%20Sheet.pdf CS-101564-DSP10 BlueCore4-ROM Product Data Sheet.pdf]<br />
* Driver: Stock Linux Kernel BlueZ<br />
* Connected to: S3C2442 USB Host controller (OHCI)<br />
* PM Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/gta01-power_control.patch<br><br />
<br />
=== Bluetooth аудио ===<br />
This one is wired via PCM bus from the CSR Bluetooth chip to the Wolfson codec.<br><br />
<br />
== Модуль WiFi ==<br />
<br />
Accton (WLAN 802.11b/g SiP-M WM3236AQ(Flash Ver:2.0 Atheros AR6001GZ)<br />
* Connected to: S3C2442 SDIO Host controller<br><br />
* Datasheet: [http://www.accton.com/products/Datasheet/WM3236A.AQ.pdf Accton 3236AQ datasheet]<br><br />
* Driver: http://svn.openmoko.org/developers/sameo/patches/<br><br />
<br />
== Виброзвонок ==<br />
* Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/gta01-vibrator.patch<br />
* Connected to: S3C2442 GPIO<br />
<br />
== Хост USB ==<br />
The USB Host controller is inside the S3C2442<br />
* Driver: Stock Linux kernel ohci_hcd<br />
* USB version 1.1<br />
* Supply USB 5v in Host mode using usb power switch AAT1275IRN-5.0-T1<br />
** http://www.analogictech.com/products/digitalfiles/AAT1275.pdf<br />
* A net EN_USBHOST is controlled by PMU GPIO "GPO", this one signal when asserted (high)<br />
** enables generation of 5V for external device using a charge pump<br />
** enables connection of 15K pulldowns to D+ and D- to allow device insertion and removal detection for host mode<br />
** DISABLES the path for USB power to charge the battery<br />
<br />
It should also be possible to use host mode with externally-provided power. This will allow the FreeRunner to be connected to a USB device and be powered and charging the battery if present at the same time.<br />
<br />
* Connect 0V, d+, d-, +5 to your USB device<br />
* Connect a 15k ohm resistor between d+ and ground<br />
* Connect a 15k ohm resistor between d- and ground<br />
* Connect 0V, +5 to your >1A power source<br />
** If your power source was not the Openmoko 1A charger, additionally connect a 47K ohm 5% resistor between the ID pin and ground to pretend to be the 1A charger.<br />
<br />
In addition you need to make sure EN_USBHOST signal that enables the physical Host mode power generation and disables the USB -> PMU charging path is deasserted. This may be taken care of automatically shortly by detection of the 48K resistor on a USB insertion leading to forcing EN_USBHOST deasserted. The charge pump that generates the 5V in host mode doesn't seem to mind getting external 5V given to it, but the real issue is that the battery will not be charged at all if we leave EN_USBHOST asserted since one of its jobs is to stop that happening.<br />
<br />
== Устройство USB ==<br />
The USB Device controller is inside the S3C2442 <br />
* Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/s3c2410_udc.patch<br />
* Please see [[USB Product IDs]] on information about which Vendor/Product IDs we use<br />
* 1200mAh lithium battery charges when connected to powered host.<br />
* Mini-AB connector similar to [http://www.cypressindustries.com/shoponline/proddetail.asp?prod=CCMUSBAB-32005-700&cat=34 this one].<br />
<br />
== Устройство I2C ==<br />
I2C is a simple communication standard intended to move small amounts of data a few inches between chips.<br />
Please see [[I2C | Neo I2C Devices]] for more information & a list of devices & the addresses currently in use & documented for the Neo1973.<br><br />
<br />
== Аудио ==<br />
See also: [[Neo1973 Audio Subsystem]]<br />
<br />
=== Кодек Wolfson ===<br />
There's a [[WM8753]] Wolfson Microelectronics CODEC (This is not a 'smart' codec that can interpret MP3/... it is a simple dumb 'sound card'.<br />
* Product Homepage: http://www.wolfsonmicro.com/products/WM8753/<br />
* Data Sheet: [http://www.wolfsonmicro.com/uploads/documents/en/WM8753.pdf WM8753.pdf]<br />
* Connected to: S3C2442 IIS interface (PCM data), S3C2442 I2C (Control)<br />
* Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/asoc.patch<br />
<br />
=== Монофонический усилитель ===<br />
There's a National Semiconductor [[LM4853]] Mono Amplifier at the analog audio output of the WM8753<br />
<br />
* Product Homepage: [http://www.national.com/pf/LM/LM4853.html LM4853.html]<br />
* Data Sheet: [http://www.national.com/ds.cgi/LM/LM4853.pdf LM4853.pdf]<br />
* Connects to (LM4853 pin): <br />
** S3C2442 GPIO: HP_IN, AMP_SHUT (shutdown); <br />
** Wolfson WM8753: LOUTL (LEFTIN), LOUTR (RIGHTIN); <br />
** speaker4102: (LEFTOUT/BLTOUT-, BLTOUT+);<br />
** headset-jack: ring 2 (RIGHTOUT), ring 3 (LEFTOUT/BLTOUT-) via 1uF-33R each<br />
<br />
=== Аналоговые проводные наушники ===<br />
There's a four-ring 2.5mm stereo jack which provides connectivity to old-fashioned wired headsets.<br />
<br />
The headsets used by Motorola smartphones (A780,A1200, ...) and the V-360 have a compatible configuration.<br />
<br />
ring<br><br />
1(base): GND<br><br />
2: right out<br><br />
3: left out<br><br />
4(tip): mic + HOLD-button(press:short to GND)<br />
<br />
=== Кнопочки ===<br />
The Neo1973 GTA02 features two buttons:<br />
* [[Neo1973 Power Button|The Power Button]]<br />
* [[Neo1973 AUX Button|The "Aux" button]]<br />
<br />
== Корпус ==<br />
The case for the FreeRunner is all black, as seen on the front page of the wiki.<br />
<br />
Openmoko has released the CAD files for the case schematics for the Openmoko [[Neo1973]] (GTA01) and Neo FreeRunner. These are available in the original Pro/E (.asm/.prt) format and alternative formats created from the originals.<br />
<br />
We welcome your assistance in providing other formats. If you are able to convert CAD files from Pro/E format to other formats, please contact [mailto:michael@openmoko.org]. We are especially interested in the DXF format and in images rendered from these files.<br />
<br />
* [http://downloads.openmoko.org/CAD/NeoFreeRunner_ProE.zip The original Pro/E (.asm/.prt) format]<br />
<br />
[http://downloads.openmoko.org/CAD/ Browse CAD directory]<br />
<br />
=Аксессуары=<br />
<br />
== Стилус ==<br />
<br />
Using 4 in 1 laser pen<br />
*Vendor: [http://www.quarton.com/laser_pen.html Quarton XPII]<br />
*GTA02 standard setup comes with [http://www.quarton.com.tw/laser_pen_infiniter_xp_2.html QUARTON XPII 4 in 1 laser pen]<br />
<br />
== Батарея ==<br />
The [[Neo FreeRunner (GTA02) Battery]] is mechanically and electrically compatible with the [[Neo1973 GTA01 Battery]], as well as limited compatibility with a Nokia BL6C battery.<br />
According to [http://lists.openmoko.org/pipermail/community/2007-February/003758.html this] post on the mailinglist.<br />
[http://wiki.openmoko.org/index.php?title=Image:Neo1973-with-BL5C-battery.png Photo] of the battery inside the Neo1973.<br />
<br />
* GTA02 using the smart battery based on TI bq27000 chipset<br />
* SANYO UF653450S 1200mAh cell.<br><br />
* Battery schematics: [http://people.openmoko.org/tony_tu/GTA02/hardware/GTA02/CT-GTA02.pdf GTA02 Smart Battery Schematics]<br />
<br />
== Карта microSD ==<br />
<br />
GTA02 should come with one of following microSD card<br />
<br />
* [http://www.transcendusa.com/ Transcend] 512MB microSD card<br />
* [http://www.sandisk.com/ SanDisk] 512MB microSD card<br><br />
<br />
== Зарядное устройство ==<br />
<br />
AKII Technology Charger<br />
<br />
*Model: [http://www.ak2.com.tw/pd_main.asp?sg_id=11 A10P1-05MP]<br />
*Input: 100-240v~ /0.3A<br />
*Output: +5v up to 2.0A<br />
*Add 47.5k 1% resistor between ID pin and ground for openmoko charger identification<br><br />
<br />
= История =<br />
<br />
== GTA02v1 ==<br />
First generation of prototypes that was given to internal Openmoko software developers. Total 30 pcs fabricated.<br />
<br />
*It is working just fine, but still based on 2440, with external NAND/SDRAM and no NOR flash<br />
*Using the PCF50633 05 N3 due to 04 N3 not available, re-work power for basic schematics verification<br />
*Using GTA01 SIM socket<br />
*Add external debug port<br />
*Still using Global locate A-GPS<br />
* ATAG_REVISION: 0310<br />
<br />
== GTA02v2 ==<br />
Second generation of prototypes, Total 50 pcs run at Taipei SMT factory MOUNT<br />
<br />
*Ideal is have 256 MB NAND on Samsung package, Due to chip availability Start using S3C2442 B43<br />
*Using correct PMU PCF50633 04 N3<br />
*Change new SIM socket<br />
*Change to u-blox A-GPS<br />
*Change LCM power from 3.3v to 1.8v<br />
*USB power switch layout/pin assignment mistake, could not verify USB host supply 5v function<br />
*GPS function verified ok with good sensitivity<br />
* ATAG_REVISION: 0320<br />
<br />
== GTA02v3 ==<br />
Production verification version, 2007/10/11 28 pcs fabricate at FIC SuZhou<br />
<br />
*Still using S3C2442 B43 for hardware verification<br />
*Using control pilot run to verify S3C2442 B54 chips<br><br />
* ATAG_REVISION: 0330<br />
<br />
== GTA02v4 ==<br />
Mass production release candidate version 1<br />
<br />
2 weeks after v3 gerber out, release the v4 gerber, and 2007/10/20 20 pcs fabricate at FIC SuZhou <br />
<br />
*Change LCM power from 1.8v to 3.3v for display stability issue<br />
*fabricate another 200 pcs for yield rate/production verification<br />
*fabricate 50 pcs with S3C2442 B43 (128 MB NAND) for quality comparsion<br />
*USB host power chip have some output voltage stability issues with Vb/Vcc comes from different power source, need layout change to fix the issue<br />
*Battery Coulomb design not working on A4<br />
* ATAG_REVISION: 0340<br />
<br />
== GTA02v5 ==<br />
Mass production candidate version 2/Mass production version<br />
<br />
* First batch fabricate 2008/1/14 at FIC SuZhou<br />
* Mass production A5 trial run start from 2008 March, including some resistor/capacitor change compare with inital 100 pcs prototypes A5, and prototypes for GTA02 developers was tracked in the [[Prototypes| Prototypes Page]]<br />
* Coulomb counter issue fixed<br />
* USB host power switch fixed<br />
* Need add capacitor for PMU Vbat input for stability issue, this could be done by direct SMT or hand rework<br />
* Need rework (still using SMT in production) add capacitor for PMU Vbat input for PMU stability issue.<br />
* Need manual rework GSM IR UART path a 100k pull down for better GSM deep sleep<br />
* ATAG_REVISION: 0350<br />
<br />
===GTA02 mass Production version change list===<br />
*PMU's LED power error: PMU potential damage issue<br />
*NOR FLASH enable WP: User can write data into NOR FLASH.<br />
*CE CS/RS fine tune: Audio's background noise too high<br />
*I2C pull high resistor: The resistor is too high and signal is distorted <br />
*GSM leakage current: TX_MODEM has a pull high resistor on IO_3V3<br />
*Power consumption: Disable keep active function<br />
*SDIO clock and esd protect resistor<br />
*Refer to Datasheet: R1526 to 33K<br />
*GSM modem on pin: The R1018 is too small and has some leakage current<br />
*LED driving transistor: When GPIO is on, the transistor will be draw more current on LED. This is component change fix, do not need change PCB or re-work.<br />
<br />
== GTA02v6 ==<br />
Mass production candidate version 3/Mass production version<br><br />
<br />
A6 will be fine tune version of A5, only minor schematic change for better product quality and version control. Capacitor and resistor change A6 also on mass production A5<br><br />
<br />
*First 100 pcs start from 2008 mid April, and factory make component placement mistake on GSM, second 100 pcs PCB arrive time TBD. <br />
*Add capacitor space for Vbat, reduce the SMT effort<br />
*Add GSM IR resistor for better GSM deep sleep<br />
*Reserve 3 GPIO for hardware version control<br />
*Fixed LEDs power usage (from about 150mW of v5 to about 25mW)<br />
* ATAG_REVISION: 0360<br />
<br />
=== GTA02 A5 to A6 changes ===<br />
*Power Glitch on VB_SYS: Add capacitor on layout, Mass production A5 also apply this change.<br />
*G-sensor separate these interrupt pins: At A5, each accelerometer INT1/INT2 connected to same line, at A6 only INT1 was connected.<br />
*GSM_modem power source Reduce power's ripple when the phone is talking<br />
*Keep active Disable keep active function, just fine tune<br />
*GPIO for version control <br />
*GSM RX_IR has some noise Add resistor and reduce GSM RX_IR noise and gsm can't enter suspend mode easily, apply on mass production A5.<br />
*LED driving transistor apply on mass production A5.<br />
*LCM's VDDIO We can totally power off LCM's power, save about extra 1mA.<br />
<br />
= Отладочная плата =<br />
<br />
== Описание соединения отладочной платы ==<br />
<br />
This is the connector used to connect the [[Debug Board]] and possibly other hardware.<br />
<br />
Connections are:<br />
* 39 - GND<br />
* 38 - STDI<br />
* 37 - _RESET<br />
* 36 - STMS<br />
* 35 - STCK<br />
* 34 - STDO<br />
* 33 - GSM_EN<br />
* 29 - _STRST<br />
* 19 - X_I2C_SCL (H-TP4703)<br />
* 18 - X_I2C_SDA (H-TP4704)<br />
* 17 - SPI_CLK0<br />
* 16 - SPI_MOSI0<br />
* 15 - SPI-MISO0 <br />
* 14 - SS0<br />
* 13 - EINT3 (H-TP4705)<br />
* 3 - CONSOLE_TXD (H-TP4701)<br />
* 2 - CONSOLE_RXD (H-TP4702)<br />
<br />
Information from [http://people.openmoko.org/roh/Debugport_GTA01bv4.png].<br />
<br />
= Отличия аппаратных изменений =<br />
== Inside the [[Bootloader]] ==<br />
Every hardware revision has its own u-boot image type. Thus, the bootloader has the revision hard-coded.<br />
The hardware revision is passed on to the kernel via the ATAG mechanism (ATAG_REVISION)<br />
<br />
== Inside the [[Kernel]] ==<br />
The kernel receives the ATAG_REVISION during bootup, and saves its contents in the "system_rev" global variable.<br />
<br />
== From Userspace ==<br />
The kernel exports the system_rev variable in /proc/cpuinfo as "Revision :" line.<br />
<br />
= Certification =<br />
<br />
== FCC ==<br />
*For US Import<br />
** 850/1800/1900 Band, FCC ID: EUNGTA02<br />
** 900/1800/1900 Band, FCC ID: EUNGTA02E<br />
** [http://people.openmoko.org/tony_tu/GTA02/certificate/EUNGTA02_850_1800_1900/ FCC test report(GTA02)]<br />
** [http://people.openmoko.org/tony_tu/GTA02/certificate/EUNGTA02E_900_1800_1900/ FCC test report(GTA02E)]<br />
<br />
== CE ==<br />
*For Europe<br />
**Registration number: M528583V-EO<br />
**[http://people.openmoko.org/tony_tu/GTA02/certificate/CE/ CE report and certificate]<br />
<br />
== NCC ==<br />
*For Taiwan Import<br />
**NCC certification number: CCAF08DG0080T0 <br />
**[http://people.openmoko.org/tony_tu/GTA02/certificate/NCC NCC report and certificate]<br />
<br />
[[Category:Neo FreeRunner Hardware/ru]]</div>DolfjeBot1http://openmoko.org/wiki/Neo_FreeRunner_GTA02_Hardware/itNeo FreeRunner GTA02 Hardware/it2008-08-31T12:48:31Z<p>DolfjeBot1: Replacing 'Freerunner' with 'FreeRunner'</p>
<hr />
<div>{{Languages|Neo FreeRunner GTA02 Hardware}}<br />
__NOTOC__<br />
__NOEDITSECTION__<br />
{{gta02menu}}<br />
Openmoko is a software distribution stack that sits on top of a [[hardware]] platform. The [[Neo FreeRunner]] phone is the second hardware platform to take advantage of Openmoko. You can find specifications of the hardware by reviewing this introduction page and the pages in the category as shown at the bottom of this page.<br />
<br />
<!-- {{note|This page is about hardware that is currently in '''design/prototype''' phase, changes are frequent}} --><br />
<br />
=Summary=<br />
Openmoko, Inc. ha costruito uno smarth phone basato su Linux compatibile pienamente con il codice d'origine per Openmoko, sotto licenza GPL, progetto chiamato GTA02 (Neo FreeRunner).<br />
<br />
Qui sotto può essere trovata una lista dettagliata dei componenti hardware.Leggi anche [[Neo FreeRunner GTA02 Hardware Requirements]] usato per creare questa selezione di componenti.<br />
<br />
<gallery><br />
Image:Gta02a5 pcba cs.JPG|display (top) side NOTE: GTA02 A5 PCBA foto lato Componenti<br />
Image:Gta02a5 pcba ps.JPG|component (back) side NOTE: GTA02 A5 PCBA foto lato Stampato<br />
Image:GTA02 A5 PCB CS.jpg|component (back) side NOTE: GTA02 A5 PCB foto lato Componenti<br />
Image:GTA02 A5 PCB PS.jpg|component (back) side NOTE: GTA02 A5 PCB foto lato Stampato<br />
Image:SimpleComponentDiagram.jpg|Diagramma Semplificato dei Componenti Hardware<br />
</gallery><br />
<br />
= GTA02 Selezione Componenti Hardware =<br />
<br />
== Dimensioni ==<br />
* 120.7 x 62 x 18.5 mm (4.75 x 2.44 x 0.728 inch)<br />
* 110 +/- 5 g (4 oncie) senza batteria <br><br />
<br />
== Componenti Principali ==<br />
=== Processore ===<br />
Il processore principale (CPU) è un [[Samsung S3C2442B B54]] (400 MHz)<br />
<br />
GPIO Assignmenti: https://svn.openmoko.org/trunk/doc/hardware/GTA02v4/gpio.txt<br />
<br />
=== Risorse Energia ===<br />
Un NXP PCF50633 04 N3 è usato per [[Neo1973_Power_Management|power management]].<br />
<br />
* NXP PMU index: [http://www.nxp.com/products/power_management/pmu/index.html NXP PMU index page]<br><br />
* Product Datasheet: [http://people.openmoko.org/tony_tu/GTA02/datasheet/PMU/PCF50633DS_02.pdf NXP PCF50633 Product Data Sheet]<br><br />
* Manuale del prodotto per l'utente: [http://people.openmoko.org/tony_tu/GTA02/datasheet/PMU/PCF50633UM_6.pdf NXP PCF50633 User Manual]<br><br />
**Un ringraziamento speciale a NXP per aver fornito pien manuale e supporto aperto a tutti gli sviluppatori<br />
**Datasheet/User manual usage [http://lists.openmoko.org/pipermail/community/2008-March/013898.html was legally authorized by NXP]<br />
* Connected to: S3C2442 via I2C, client address is 0x08. <br><br />
* Driver Source: https://svn.openmoko.org/trunk/src/target/kernel/patches/pcf50633.patch<br><br />
<br />
=== Flash ===<br />
==== NAND Flash ====<br />
256MB integrata Samsung NAND flash all'interno del 2442 multi-chip package, attaccato al S3C2442 NAND controller<br />
<br />
* Homepage del prodotto: [http://www.samsung.com/global/business/semiconductor/productInfo.do?fmly_id=229&partnum=SC32442 S3C2442]<br />
* Data Sheet: S3C2442 B54 comes with 256 MB NAND MCP package<br />
* Connesso a: S3C2442 NAND controller<br><br />
<br />
==== NOR Flash ====<br />
<br />
16MBit ST M58WR016KB706E NOR flash for 'unbrickable emergency boot' feature.<br />
<br />
* Product Homepage: [http://www.st.com/stonline/products/families/memories/fl_nor_mob/index.htm ST Mobile Flash NOR/Mobile Terminal]<br />
* Data Sheet: [http://www.st.com/stonline/products/literature/ds/13023/m58wr032qb.pdf M58WR016]<br />
* Connected to: S3C2442 NAND controller<br><br />
<br />
=== SDRAM ===<br />
128MB SDRAM (64MB inside 2442 MCP, 1x Samsung K4M51323PC) attached to S3C2442 SDRAM controller<br />
* Product Homepage: [http://www.samsung.com/global/business/semiconductor/productInfo.do?fmly_id=136&partnum=K4M51323PC Samsung K4M51323PC]<br />
* Data Sheet: [http://www.samsung.com/global/system/business/semiconductor/product/2007/6/11/MobileSDRAM/MobileSDRSDRAM/512Mbit/K4M51323PC/ds_k4m51323pc.pdf Samsung K4M51323PC]<br />
* Connected to: S3C2442 <br><br />
<br />
== GSM/GPRS ==<br />
The [[GSM]] (including GPRS) modem is Texas Instruments Calypso based.<br />
<br />
* Connected to: S3C2442 UART1 (full-uart, RxD, TxD, CTS, RTS), /dev/ttySAC0 in userspace<br />
* PM Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/gta01-power_control.patch<br />
* Accessible GSM/GPRS antenna jack (if battery cover is removed)<br><br />
<br />
=== CALYPSO ASIC digital baseband ===<br />
Unfortunately we cannot provide many details on the GSM chipset due to very tight [http://en.wikipedia.org/wiki/Non-disclosure_agreement NDA]s. However, this is not neccessarily required, since it interfaces using a standard UART serial line with the S3C2442. On that interface, [http://www.3gpp.org/ftp/Specs/archive/07_series/07.05/ GSM 07.05], [http://www.3gpp.org/ftp/Specs/archive/07_series/07.10/ GSM 07.10] and other standardized protocols are used.<br />
<br />
The NDAd documentation for the calypso, [http://cryptome.org/ti-calypso1.pdf register definition ] and [http://cryptome.org/ti-calypso2.pdf hardware definition ] was leaked onto a public forum on the 4th of March by persons or persons unknown.<br />
The legality of reading these files may vary according to your local laws, as may generating code from them.<br />
<br />
<br />
*Calypso D751992AZHH<br><br />
*The firmware within GTA02 should be moko6 or later (internal code name)<br />
<br />
=== TI TWL3025BZGMR analog baseband ===<br />
*Product Homepage: [http://focus.ti.com/general/docs/wtbu/wtbuproductcontent.tsp?templateId=6123&navigationId=12295&contentId=4703 TWL3014]<br><br />
<br />
=== TI TRF6151 (GSM/PCS) RF Transceiver ===<br />
*Product Homepage: [http://focus.ti.com/general/docs/wtbu/wtbuproductcontent.tsp?templateId=6123&navigationId=12296&contentId=4701 TRF6151] <br><br />
GPRS Class12/CS4 <br><br />
<br />
== AGPS ==<br />
[[u-blox ANTARIS 4 ATR0635]] chip<br />
* Connected to: S3C2442 UART2, /dev/ttySAC1 in userspace<br />
<br />
== Accelerometers ==<br />
Two ST LIS302DL<br />
* Homepage: http://www.st.com/stonline/products/literature/ds/12726/lis302dl.htm<br />
* Datasheet: http://www.st.com/stonline/products/literature/ds/12726.pdf<br />
* Connected to: S3C2442 via SPI interface<br />
* S3C2442 SPI EINT interrupt inputs<br><br />
<br />
== Graphics/3D Acceleration ==<br />
<br />
Smedia Glamo 3362.<br />
* Homepage: http://www.smediatech.com/product3362.htm<br />
* Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/smedia-glamo.patch<br />
* Data sheet: This is not available, as it is under NDA. It will likely never be available. (Source: Raster - IRC). There is hope that the glamo chip features may be usable even without a NDA, see [http://unadventure.wordpress.com/2008/06/08/accelerating-in-my-pocket/ the hack here]<br />
* Connected to: S3C2442 Address/Data bus <br><br />
<br />
=== microSD ===<br />
The GTA02 has one microSD aka Transflash slot. Using the Glamo 3362 MMC/SD controller<br />
<br />
*It should support SDHC, and 4GB card has been tested. Anyone with 8GB card? MicroSD slot is [[Disassembling_Neo1973#Opening_back_cover|under battery]].<br />
* Connected to: Glamo 3362 MMC/SD controller<br />
* Driver: Check svn for the SMedia driver with SD implementation<br />
* [[Supported microSD cards]]<br />
* Specifications: [http://www.sdcard.org/about/memory_card/pls/ SD Simplified Specification], [http://www.mmca.org/compliance/buy_spec/AN_MMCA050419.pdf MMC (partial)], [http://www.sandisk.com/Assets/File/OEM/Manuals/manual-rs-mmcv1.0.pdf MMC (product manual)]<br />
* SANDISK 128 MB/512 MB and some 4G SDHC card been verified could work on GTA02<br><br />
<br />
== LCD Module (LCM) ==<br />
Toppoly (tpo) 2.8" diagonal (1.7" x 2.27" - 43mm x 58mm) 480x640 TD028TTEC1 module, using a Toshiba JBT6K74 TFT <br />
LCD Driver Chipset.<br><br />
* Homepage: [http://www.tpo.biz/ENG/business-eng/Activer-Matrix-VGA.htm Activer-Matrix-VGA.htm]<br />
* Specification: FIXME<br />
* Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/gta01-jbt6k74.patch<br />
* Backlight Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/gta01-backlight.patch<br />
* Connected to: Glamo3362 LCM interface and Glamo3362 SPI Interface<br><br />
<br />
==== Touch Screen ====<br />
* Connected to: S3C2442 TS controller<br />
* Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/s3c2410_touchscreen.patch<br />
<br />
== Bluetooth Module==<br />
Delta DFBM-CS320 Class2 Module, using CSR BlueCore4<br />
<br />
* Data Sheet: [http://www.delta.com.tw/product/cp/vco/BT/download/pdf/CS/2.DFBM-CS320.pdf 2.DFBM-CS320.pdf]<br />
* CSR Data Sheet: [http://www.csrsupport.com/download/2302/CS-101564-DSP10%20BlueCore4-ROM%20Product%20Data%20Sheet.pdf CS-101564-DSP10 BlueCore4-ROM Product Data Sheet.pdf]<br />
* Driver: Stock Linux Kernel BlueZ<br />
* Connected to: S3C2442 USB Host controller (OHCI)<br />
* PM Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/gta01-power_control.patch<br><br />
<br />
=== Bluetooth Audio ===<br />
This one is wired via PCM bus from the CSR Bluetooth chip to the Wolfson codec.<br><br />
<br />
== WiFi Module==<br />
<br />
Accton (WLAN 802.11b/g SiP-M WM3236AQ(Flash Ver:2.0 Atheros AR6001GZ)<br />
* Connected to: S3C2442 SDIO Host controller<br><br />
* Datasheet: [http://www.accton.com/products/Datasheet/WM3236A.AQ.pdf Accton 3236AQ datasheet]<br><br />
* Driver: http://svn.openmoko.org/developers/sameo/patches/<br><br />
<br />
== Vibrator ==<br />
* Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/gta01-vibrator.patch<br />
* Connected to: S3C2442 GPIO<br />
<br />
== USB Host ==<br />
The USB Host controller is inside the S3C2442<br />
* Driver: Stock Linux kernel ohci_hcd<br />
* USB version 1.1<br />
* Supply USB 5v in Host mode using usb power switch AAT1275IRN-5.0-T1<br />
** http://www.analogictech.com/products/digitalfiles/AAT1275.pdf<br />
* A net EN_USBHOST is controlled by PMU GPIO "GPO", this one signal when asserted (high)<br />
** enables generation of 5V for external device using a charge pump<br />
** enables connection of 15K pulldowns to D+ and D- to allow device insertion and removal detection for host mode<br />
** DISABLES the path for USB power to charge the battery<br />
<br />
It should also be possible to use host mode with externally-provided power. This will allow the FreeRunner to be connected to a USB device and be powered and charging the battery if present at the same time.<br />
<br />
* Connect 0V, d+, d-, +5 to your USB device<br />
* Connect a 15k ohm resistor between d+ and ground<br />
* Connect a 15k ohm resistor between d- and ground<br />
* Connect 0V, +5 to your >1A power source<br />
** If your power source was not the Openmoko 1A charger, additionally connect a 47K ohm 5% resistor between the ID pin and ground to pretend to be the 1A charger.<br />
<br />
In addition you need to make sure EN_USBHOST signal that enables the physical Host mode power generation and disables the USB -> PMU charging path is deasserted. This may be taken care of automatically shortly by detection of the 48K resistor on a USB insertion leading to forcing EN_USBHOST deasserted. The charge pump that generates the 5V in host mode doesn't seem to mind getting external 5V given to it, but the real issue is that the battery will not be charged at all if we leave EN_USBHOST asserted since one of its jobs is to stop that happening.<br />
<br />
== USB Device ==<br />
The USB Device controller is inside the S3C2442 <br />
* Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/s3c2410_udc.patch<br />
* Please see [[USB Product IDs]] on information about which Vendor/Product IDs we use<br />
* 1200mAh lithium battery charges when connected to powered host.<br />
* Mini-AB connector similar to [http://www.cypressindustries.com/shoponline/proddetail.asp?prod=CCMUSBAB-32005-700&cat=34 this one].<br />
<br />
== I2C Devices ==<br />
I2C is a simple communication standard intended to move small amounts of data a few inches between chips.<br />
Please see [[I2C | Neo I2C Devices]] for more information & a list of devices & the addresses currently in use & documented for the Neo1973.<br><br />
<br />
== Audio ==<br />
See also: [[Neo1973 Audio Subsystem]]<br />
<br />
=== Wolfson Codec ===<br />
There's a [[WM8753]] Wolfson Microelectronics CODEC (This is not a 'smart' codec that can interpret MP3/... it is a simple dumb 'sound card'.)<br />
* Product Homepage: http://www.wolfsonmicro.com/products/WM8753/<br />
* Data Sheet: [http://www.wolfsonmicro.com/uploads/documents/en/WM8753.pdf WM8753.pdf]<br />
* Connected to: S3C2442 IIS interface (PCM data), S3C2442 I2C (Control)<br />
* Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/asoc.patch<br />
<br />
=== Mono Amplifier ===<br />
There's a National Semiconductor [[LM4853]] Mono Amplifier at the analog audio output of the WM8753<br />
<br />
* Product Homepage: [http://www.national.com/pf/LM/LM4853.html LM4853.html]<br />
* Data Sheet: [http://www.national.com/ds.cgi/LM/LM4853.pdf LM4853.pdf]<br />
* Connects to (LM4853 pin): <br />
** S3C2442 GPIO: HP_IN, AMP_SHUT (shutdown); <br />
** Wolfson WM8753: LOUTL (LEFTIN), LOUTR (RIGHTIN); <br />
** speaker4102: (LEFTOUT/BLTOUT-, BLTOUT+);<br />
** headset-jack: ring 2 (RIGHTOUT), ring 3 (LEFTOUT/BLTOUT-) via 1uF-33R each<br />
<br />
=== Analog wired Headset ===<br />
There's a four-ring 2.5mm stereo jack which provides connectivity to old-fashioned wired headsets.<br />
<br />
The headsets used by Motorola smartphones (A780,A1200, ...) and the V-360 have a compatible configuration.<br />
<br />
ring<br><br />
1(base): GND<br><br />
2: right out<br><br />
3: left out<br><br />
4(tip): mic + HOLD-button(press:short to GND)<br />
<br />
=== Buttons ===<br />
The Neo1973 GTA02 features two buttons:<br />
* [[Neo1973 Power Button|The Power Button]]<br />
* [[Neo1973 AUX Button|The "Aux" button]]<br />
<br />
== Case ==<br />
The case for the FreeRunner is all black, as seen on the front page of the wiki.<br />
<br />
Openmoko has released the CAD files for the case schematics for the Openmoko [[Neo1973]] (GTA01) and Neo FreeRunner. These are available in the original Pro/E (.asm/.prt) format and alternative formats created from the originals.<br />
<br />
We welcome your assistance in providing other formats. If you are able to convert CAD files from Pro/E format to other formats, please contact [mailto:michael@openmoko.org]. We are especially interested in the DXF format and in images rendered from these files.<br />
<br />
* [http://downloads.openmoko.org/CAD/NeoFreeRunner_ProE.zip The original Pro/E (.asm/.prt) format]<br />
<br />
[http://downloads.openmoko.org/CAD/ Browse CAD directory]<br />
<br />
=Accessory=<br />
<br />
== Stylus ==<br />
<br />
Using 4 in 1 laser pen<br />
*Vendor: [http://www.quarton.com/laser_pen.html Quarton XPII]<br />
*GTA02 standard setup comes with [http://www.quarton.com.tw/laser_pen_infiniter_xp_2.html QUARTON XPII 4 in 1 laser pen]<br />
<br />
== Battery ==<br />
The [[Neo FreeRunner (GTA02) Battery]] is mechanically and electrically compatible with the [[Neo1973 GTA01 Battery]], as well as limited compatibility with a Nokia BL6C battery.<br />
According to [http://lists.openmoko.org/pipermail/community/2007-February/003758.html this] post on the mailinglist.<br />
[http://wiki.openmoko.org/index.php?title=Image:Neo1973-with-BL5C-battery.png Photo] of the battery inside the Neo1973.<br />
<br />
* GTA02 using the smart battery based on TI bq27000 chipset<br />
* SANYO UF653450S 1200mAh cell.<br><br />
* Battery schematics: [http://people.openmoko.org/tony_tu/GTA02/hardware/GTA02/CT-GTA02.pdf GTA02 Smart Battery Schematics]<br />
<br />
== microSD Card ==<br />
<br />
GTA02 should come with one of following microSD card<br />
<br />
* [http://www.transcendusa.com/ Transcend] 512MB microSD card<br />
* [http://www.sandisk.com/ SanDisk] 512MB microSD card<br><br />
<br />
== Charger ==<br />
<br />
AKII Technology Charger<br />
<br />
*Model: [http://www.ak2.com.tw/pd_main.asp?sg_id=11 A10P1-05MP]<br />
*Input: 100-240v~ /0.3A<br />
*Output: +5v up to 2.0A<br />
*Add 47.5k 1% resistor between ID pin and ground for openmoko charger identification<br><br />
<br />
= History =<br />
<br />
== GTA02v1 ==<br />
First generation of prototypes that was given to internal Openmoko software developers. Total 30 pcs fabricated.<br />
<br />
*It is working just fine, but still based on 2440, with external NAND/SDRAM and no NOR flash<br />
*Using the PCF50633 05 N3 due to 04 N3 not available, re-work power for basic schematics verification<br />
*Using GTA01 SIM socket<br />
*Add external debug port<br />
*Still using Global locate A-GPS<br />
* ATAG_REVISION: 0310<br />
<br />
== GTA02v2 ==<br />
Second generation of prototypes, Total 50 pcs run at Taipei SMT factory MOUNT<br />
<br />
*Ideal is have 256 MB NAND on Samsung package, Due to chip availability Start using S3C2442 B43<br />
*Using correct PMU PCF50633 04 N3<br />
*Change new SIM socket<br />
*Change to u-blox A-GPS<br />
*Change LCM power from 3.3v to 1.8v<br />
*USB power switch layout/pin assignment mistake, could not verify USB host supply 5v function<br />
*GPS function verified ok with good sensitivity<br />
* ATAG_REVISION: 0320<br />
<br />
== GTA02v3 ==<br />
Production verification version, 2007/10/11 28 pcs fabricate at FIC SuZhou<br />
<br />
*Still using S3C2442 B43 for hardware verification<br />
*Using control pilot run to verify S3C2442 B54 chips<br><br />
* ATAG_REVISION: 0330<br />
<br />
== GTA02v4 ==<br />
Mass production release candidate version 1<br />
<br />
2 weeks after v3 gerber out, release the v4 gerber, and 2007/10/20 20 pcs fabricate at FIC SuZhou <br />
<br />
*Change LCM power from 1.8v to 3.3v for display stability issue<br />
*fabricate another 200 pcs for yield rate/production verification<br />
*fabricate 50 pcs with S3C2442 B43 (128 MB NAND) for quality comparsion<br />
*USB host power chip have some output voltage stability issues with Vb/Vcc comes from different power source, need layout change to fix the issue<br />
*Battery Coulomb design not working on A4<br />
* ATAG_REVISION: 0340<br />
<br />
== GTA02v5 ==<br />
Mass production candidate version 2/Mass production version<br />
<br />
* First batch fabricate 2008/1/14 at FIC SuZhou<br />
* Mass production A5 trial run start from 2008 March, including some resistor/capacitor change compare with inital 100 pcs prototypes A5, and prototypes for GTA02 developers was tracked in the [[Prototypes| Prototypes Page]]<br />
* Coulomb counter issue fixed<br />
* USB host power switch fixed<br />
* Need add capacitor for PMU Vbat input for stability issue, this could be done by direct SMT or hand rework<br />
* Need rework (still using SMT in production) add capacitor for PMU Vbat input for PMU stability issue.<br />
* Need manual rework GSM IR UART path a 100k pull down for better GSM deep sleep<br />
* ATAG_REVISION: 0350<br />
<br />
===GTA02 mass Production version change list===<br />
*PMU's LED power error: PMU potential damage issue<br />
*NOR FLASH enable WP: User can write data into NOR FLASH.<br />
*CE CS/RS fine tune: Audio's background noise too high<br />
*I2C pull high resistor: The resistor is too high and signal is distorted <br />
*GSM leakage current: TX_MODEM has a pull high resistor on IO_3V3<br />
*Power consumption: Disable keep active function<br />
*SDIO clock and esd protect resistor<br />
*Refer to Datasheet: R1526 to 33K<br />
*GSM modem on pin: The R1018 is too small and has some leakage current<br />
*LED driving transistor: When GPIO is on, the transistor will be draw more current on LED. This is component change fix, do not need change PCB or re-work.<br />
<br />
== GTA02v6 ==<br />
Mass production candidate version 3/Mass production version<br><br />
<br />
A6 will be fine tune version of A5, only minor schematic change for better product quality and version control. Capacitor and resistor change A6 also on mass production A5<br><br />
<br />
*First 100 pcs start from 2008 mid April, and factory make component placement mistake on GSM, second 100 pcs PCB arrive time TBD. <br />
*Add capacitor space for Vbat, reduce the SMT effort<br />
*Add GSM IR resistor for better GSM deep sleep<br />
*Reserve 3 GPIO for hardware version control<br />
*Fixed LEDs power usage (from about 150mW of v5 to about 25mW)<br />
* ATAG_REVISION: 0360<br />
<br />
=== GTA02 A5 to A6 changes ===<br />
*Power Glitch on VB_SYS: Add capacitor on layout, Mass production A5 also apply this change.<br />
*G-sensor separate these interrupt pins: At A5, each accelerometer INT1/INT2 connected to same line, at A6 only INT1 was connected.<br />
*GSM_modem power source Reduce power's ripple when the phone is talking<br />
*Keep active Disable keep active function, just fine tune<br />
*GPIO for version control <br />
*GSM RX_IR has some noise Add resistor and reduce GSM RX_IR noise and gsm can't enter suspend mode easily, apply on mass production A5.<br />
*LED driving transistor apply on mass production A5.<br />
*LCM's VDDIO We can totally power off LCM's power, save about extra 1mA.<br />
<br />
= Debug Board =<br />
<br />
== Debug Board Connector definition ==<br />
<br />
This is the connector used to connect the [[Debug Board]] and possibly other hardware.<br />
<br />
Connections are:<br />
* 39 - GND<br />
* 38 - STDI<br />
* 37 - _RESET<br />
* 36 - STMS<br />
* 35 - STCK<br />
* 34 - STDO<br />
* 33 - GSM_EN<br />
* 29 - _STRST<br />
* 19 - X_I2C_SCL (H-TP4703)<br />
* 18 - X_I2C_SDA (H-TP4704)<br />
* 17 - SPI_CLK0<br />
* 16 - SPI_MOSI0<br />
* 15 - SPI-MISO0 <br />
* 14 - SS0<br />
* 13 - EINT3 (H-TP4705)<br />
* 3 - CONSOLE_TXD (H-TP4701)<br />
* 2 - CONSOLE_RXD (H-TP4702)<br />
<br />
Information from [http://people.openmoko.org/roh/Debugport_GTA01bv4.png].<br />
<br />
= Distinguishing hardware revisions =<br />
== Inside the [[Bootloader]] ==<br />
Every hardware revision has its own u-boot image type. Thus, the bootloader has the revision hard-coded.<br />
The hardware revision is passed on to the kernel via the ATAG mechanism (ATAG_REVISION)<br />
<br />
== Inside the [[Kernel]] ==<br />
The kernel receives the ATAG_REVISION during bootup, and saves its contents in the "system_rev" global variable.<br />
<br />
== From Userspace ==<br />
The kernel exports the system_rev variable in /proc/cpuinfo as "Revision :" line.<br />
<br />
= Certification =<br />
<br />
== FCC ==<br />
*For US Import<br />
** 850/1800/1900 Band, FCC ID: EUNGTA02<br />
** 900/1800/1900 Band, FCC ID: EUNGTA02E<br />
** [http://people.openmoko.org/tony_tu/GTA02/certificate/EUNGTA02_850_1800_1900/ FCC test report(GTA02)]<br />
** [http://people.openmoko.org/tony_tu/GTA02/certificate/EUNGTA02E_900_1800_1900/ FCC test report(GTA02E)]<br />
<br />
== CE ==<br />
*For Europe<br />
**Registration number: M528583V-EO<br />
**[http://people.openmoko.org/tony_tu/GTA02/certificate/CE/ CE report and certificate]<br />
<br />
== NCC ==<br />
*For Taiwan Import<br />
**NCC certification number: CCAF08DG0080T0 <br />
**[http://people.openmoko.org/tony_tu/GTA02/certificate/NCC NCC report and certificate]<br />
<br />
[[Category:Neo FreeRunner Hardware/it]]</div>DolfjeBot1http://openmoko.org/wiki/Neo_FreeRunner_GPS_Software_Fix_Test_ReportNeo FreeRunner GPS Software Fix Test Report2008-08-31T12:48:20Z<p>DolfjeBot1: Replacing 'Freerunner' with 'FreeRunner'</p>
<hr />
<div>See [[GPS_Problems]] for details on FreeRunner GPS problems.<br />
<br />
=== Problem: it takes a long time (10min+) before the FreeRunner gets first GPS data ===<br />
<br />
It was found that the Openmoko FreeRunner GPS has a long Time To First Fix (TTFF) with the SD card in the phone. [http://lists.openmoko.org/pipermail/community/2008-July/021774.html This thread] indicates that there is interference from the SD card slot, as without the SD card inserted it the TTFF are much shorter.<br />
<br />
::More specific: the GPS signal level drops by -20dBm, i.e. factor 100. Signal strength of a GPS satellite above your head is around -127dBm. Needed strength for a first fix is -145dBm with a minimum of three satellites. Once the GPS chip has a fix, it can operate at signal levels of -157dBm, thus making it possible to operate while there is data transfer from/to the SD card.<br />
::''(From http://lists.openmoko.org/pipermail/community/2008-July/022202.html )''<br />
<br />
=== Test Enviroment ===<br />
<br />
<br />
=== Test Script === <br />
<br />
<pre><br />
<br />
</pre><br />
<br />
=== Test Result ===<br />
<br />
|-<br />
| Date || Location || Image used<br />
|-<br />
<br />
[[Category:GPS]]<br />
[[Category:Neo FreeRunner Hardware]]</div>DolfjeBot1