m (→Introduction: tidy)
m (→Q: How much?: mas->mass)
|Line 13:||Line 13:|
=== Q: How much? ===
=== Q: How much? ===
A: $350, for the developers phone - Phase 1. The
A: $350, for the developers phone - Phase 1. The market price has not been revealed.
=== Q: What will it do? ===
=== Q: What will it do? ===
Revision as of 16:05, 26 February 2007
Questions and Answers that don't seem to fit elsewhere
Q: What is OpenMoko and Neo1973?
Q: When can I buy a Neo1973?
Q: How much?
A: $350, for the developers phone - Phase 1. The mass market price has not been revealed.
Q: What will it do?
A: The Phase 1 phone available in late March is for developers only. It is not suitable for end users, it will have basic functionality as a touchscreen phone. Little else will work, software development will continue till mass market release.
Those interested should:
- Have fun hacking devices.
- Be able to find their way through prototype software and hardware without much documentation.
- Share the dream of a device powered by free software.
- Not expect a consumer-level device.
- Come up with new ideas for exploring the age of mobile computing.
- Have $350.
Ideally they also:
- Can spot bugs and submit patches.
- Love to cooperate with a community improving the software.
Q: How do I install and manage software on OpenMoko?
Q: How can I compile programs for the Neo1973?
A: See Toolchain.
Q: Is there an emulator available for OpenMoko?
*XorA guesses that if your first question is "is there an emulator" then your not actually ever going to do dev work :-)
QEMU is a good place to start, and we should be able to run almost all OpenMoko apps with it. For a good start with the QEMU emulator visit: http://www.aurel32.net/info/debian_arm_qemu.php
Jeff put together an image you can test under qemu, if you so desire: ftp://ftp.blagblagblag.org/pub/BLAG/developers/jebba/openmoko/
OpenMoko has longer term plans to port the FIC machines to QEMU. For now MACHINE="qemuarm" can be used.
Another is Xoo. Koen says: "Xoo should be enough for most apps people will develop, since most don't need access to the gsm uart directly. If you're hardcore you could use qemu + xoo, but that still doesn't emulate all the hardware quirks (e.g. unaligned access)".
Update: Stefan Schmidt has resized the Neo1973 Mock-up and written a small description for xoo. In his words:
It's not really useable at all, as you need a really high screen resolution to fit the whole picture on your screen. And of course the dpi are wrong. Even no buttons because I can't remember where they are at the case.
Start with 'xoo --device /path/to/neo1973.xml'
Or use Xephyr directly with locally compiled programs (e.g. matchbox svn + openmoko):
Xephyr -screen 480x640 -nolisten tcp -ac :1 & export DISPLAY=:1 export LD_LIBRARY_PATH=/usr/local/lib matchbox-window-manager -display $DISPLAY -use_titlebar no \ -use_super_modal yes -use_lowlight yes -use_dialog_mode static \ -use_cursor yes & matchbox-panel --geometry=480x44 --end-applets=clock & openmoko-footer & openmoko-taskmanager &
Q: Where can I find some type of tutorial for a 'Hello, world' on OpenMoko?
A: This should get you started: http://www.gtk.org/tutorial/
Q: Can PalmOS apps applications be ported to run on OpenMoko?
A: Making legacy apps written for the "Garnet" OS (née "Palm OS") run on Linux is decidedly non-trivial. An emulator for this is going to be part of the ACCESS Linux Platform.
PalmOS uses a very different model from Linux: it doesn't really have a concept of a file, per se; instead, all memory is seen as a "soup" of records to access and manipulate (this isn't strictly true, as files had to be grafted on when removable flash was supported, but it's close enough, from a developer's standpoint). Also, the GUI toolkit looks very, very different from GTK. The result is that a very well-written, modular program that carefully separates its core algorithms from its user interface and data input and output can be ported by replacing those components. A program written by a mere mortal programmer is likely to have all these components intertwined to a point that a port will be challenging to say the least.
The ACCESS Linux Platform will include POSE, an emulator that simulates a Palm device on a Linux host. This emulator has been around a long time; one expects that it will also run on OpenMoko, but this has to be considered a short-term bandaid rather than a long-term solution.
Q: What are the relevant X11 details?
A: See xdpyinfo output.
Q: Does it include a camera?
A: No, see Neo1973_Hardware for details on what it does include (and Wish_List_-_Hardware for what some want in the future.) With the USB port and a powered hub, or bluetooth, you should be able to attach many external cameras.
Q: What is the battery life?
A: There has been no word on this so far, but see these estimates for a rough idea.
Q: How heavy is it?
A: 184 +/- 5 g
Q: Why is only USB 1.1 provided?
A: The SoC handles the USB, and it's only capable of 1.1. As to why not a spiffier SoC, we presume that keeping the costs reasonable has something to do with it. But this shouldn't have too negative an impact: USB 1.1 are almost certainly OK for a phone: this is not a high-performance cluster node, just a power-saving phone. In particular, 11mps WLan works perfect with USB 1.1. I guess 54mps will work ok too, albeit perhaps a bit slower then they could.
The main problem (with more powerful SoC) is not to provide a USB2.0 host port in the device. The main problem is power. You need a pretty powerful DC/DC step-up converter to provide the 5V power supply to the USB bus. And you have to provide at least up to 100mA - but to support all devices, 500mA.
It's not a technical problem, per se.
It's just that you have to have one extra (powerful) DC/DC step-up converter in the device, something that vendors of phones (and other devices) usually don't put there for cost, battery life time and PCB footprint reasons.
Q: Can the Neo charge and use devices on a USB hub at the same time?
- When the Neo is connected to a device port on a USB hub, it will start charging. If the hub is a powered hub, then it will charge fast (3h), otherwise around 12h.
- If you plug the Neo into the host port of a USB hub you can use devices on that hub but the Neo will not charge. (Some/many USB hubs will not accept an unpowered host as valid, hence the need for the below cable.)
- This is because the host socket on USB hubs is not powered.
FIC product development is looking into providing something that conveniently solves this problem.
The USB port on the Neo is not a properly compliant USB host port, all USB host ports must provide 5V - though powered devices or hubs may not draw any current from this, they may refuse to work. (The Belkin Tetrahub is an example of a hub that will not work.)
One solution is a three headed cable.
One end plugs into the Neo. One end plugs into a device port of a powered hub, or the Neo charger. One end plugs into the host port of a hub.
The Charger/USB device plug only has +5V and 0V connected in the simple cable, which are connected to the other ends.
For a more complex cable, when the host socket is not plugged in, the cable acts as a simple USB cable.
Q: What are the details of the USB port on the Neo1973? How does it compare to USB On-The-Go?
A: The Neo1973 will have mini-USB-B, and will be able to function as either a host or a device. It will NOT be USB On-The-Go. OTG is a complex specification, and it comprises way more than just a AB socket, but also electrical and software components which cannot be provide by the S3C2410.
You will need a special Mini-B to regular-B cable (note that this won't actually comply with the USB standard: a compliant cable has to have an A or Mini-A plug on one end, and B or Mini-B on the other).
Q: What is the rationale behind the exclusion of WiFi?
A: No suitable low power open source WiFi device was available when the Neo1973 was designed. A closed source WiFi device would have been restrictive for developers and users alike. The form of wireless connectivity that is included in the Neo1973 is Bluetooth. An option that has been discussed on the mailing list(s) is to use a USB WiFi adapter. (however, the USB on the Neo1973 is unpowered.)
Neo1973 is (hopefully) the first in a long line of devices that can run OpenMoko. Future versions of the device may have wifi.
Q: Are there any LEDs on the Neo 1973?
A: The Neo1973 v1 will have no LEDs besides the screen backlight.
Q: Will a JTAG port be made available?
A: The "Hacker's Lunchbox" will make this kind of stuff easy. Details will be provided by Sean/FIC later.
Q: Can I bridge to an Ethernet (wired or unwired) network via a suitable Bluetooth enabled router?
Q: What providers in the USA provide the GSM required for Neo 1973?
Q: Will OpenMoko "Just Work" with Mac OS X?
A: There has been some discussion of this on the mailing list. There is motivation, and there are interested developers. Not being a Mac OS X user, I don't know enough to summarize the discussion to answer this question. Can someone please fill in?
A: For IP over USB cable connectivity, it is planned to improve/adapt the AJZaurusUSB driver, allowing ssh into the OpenMoko.
A: It is expected that (Bluetooth/UB) SyncML based interoperation for contacts and events can easily be achieved by a patch to the Apple iSync configuration tables.
A: There is an open source implementation of Cocoa (GNUstep) that aims to run MacOS X compatible applications (sort of PPC/x86/ARM universal binaries) on OpenMoko devices: mySTEP.
Q: On the lists on lists.openmoko.org, should replies be added above or below the original text?
A: Please reply UNDER post.
Q: How can I find out if a question or topic has already been discussed on the mailing lists?
A: By searching the mailing list archives. For example, using Google searches:
For example, to search for accelerometer:
If you only want to read the "official" mails from FIC people or from OpenMoko people:
site:openmoko.org text "at fic.com.tw" site:openmoko.org text "at openmoko.org"
For example to search for "release date" from FIC people:
site:openmoko.org "release date" "at fic.com.tw"