http://openmoko.org/api.php?action=feedcontributions&user=Bas&feedformat=atomOpenmoko - User contributions [en]2024-03-29T15:15:21ZUser contributionsMediaWiki 1.19.24http://openmoko.org/wiki/Wish_List_-_HardwareWish List - Hardware2007-10-15T07:44:08Z<p>Bas: /* TV/radio receiver */</p>
<hr />
<div>This page details hardware features which some would like to go into future phones similar to the [[Neo1973]].<br />
<br />
Related pages are:<br />
*[[Wishlist - Hardware - Novel Devices]] - openmoko will run on a large number of devices in the future, some of which may be DVD players, cameras, or convergance devices. <br />
*[[Wishlist:Unlikely]] - Hardware that is unlikely to appear in any OpenMoko device, due to it being impossible to fabricate with near-term technology, or for other reasons.<br />
*[[Wishlist:Accessories]] - Accessories that people would like, that connect easily to the phone - initially primarily for the Neo1973 <br />
*[[Wishlist:Expansion]] - add-ons to the phone, maybe involving hardware changes, and software and hardware protocols to implement these.<br />
<br />
This page is rather long. Before adding a new idea, please read through this page and the above pages, to make sure your idea has not been suggested before.<br />
<br />
==Processor==<br />
===AT91CAP9S500A (ARM9 + FPGA-port)===<br />
Why FPGA?:<br />
*[http://hardware.silicon.com/servers/0,39024647,39166443,00.htm?r=1 20 March 2007 Green supercomputer is 'go' in Scotland] Quote: "...A supercomputer 10 times more energy efficient and up to 300 times faster than its traditional equivalents..."<br />
<br />
Take a look at this microcontroller, that integrates an ARM9 microcontroller and a dedicated FPGA port: AT91CAP9S500A. It has "only" a max. clock at 200MHz, but can use a FPGA for hardware acceleration, that could be used for video (de)compression, [http://en.wikipedia.org/wiki/AacPlus_v2 aacPlus v2]/[http://en.wikipedia.org/wiki/HE-AAC_v2 HE-AAC v2] sound (de)compression and many other things. HE-AAC v2 is better than [http://en.wikipedia.org/wiki/MP3 MP3].<br />
*[http://www.atmel.com/dyn/products/product_card.asp?family_id=689&family_name=AT91CAP+Microcontrollers&part_id=4137 AT91CAP9S500A] Quote: "...The AT91CAP9S500A is built around a 12-layer bus matrix, allowing a maximum internal bandwidth of twelve 32-bit buses. Its distributed DMA architecture enables multiple data transfers to take place between the processor, memories and peripherals with minimal processor overhead...".<br />
*[http://www.atmel.com/dyn/resources/prod_documents/doc6310.pdf GNU-Based Software Development on AT91SAM Microcontrollers]<br />
*Maybe this is a good tool?: [http://www.jhdl.org/ BYU JHDL, Open Source FPGA CAD Tools]<br />
*[http://www.eetimes.com/showArticle.jhtml;?articleID=197002705 02/05/2007, FPGA tool bottleneck stalls HPC] Quote: "...Current FPGA synthesis, placement and routing tools are written for hardware designers, not software programmers simply trying to accelerate an algorithm..."<br />
<br />
This seems to be a good hardware mix (ARM+FPGA). It does [http://en.wikipedia.org/wiki/Theora Ogg Theora] or [http://en.wikipedia.org/wiki/MJPEG MJPEG] in the FPGA with 1 million gates:<br />
*http://sourceforge.net/projects/elphel, [http://wiki.elphel.com/index.php?title=10353 board 10353], [http://wiki.elphel.com/index.php?title=Camera_hardware camera hardware], [http://wiki.elphel.com/index.php?title=Main_Page Main page], [http://www.elphel.com/articles/index.html Imaging solutions with Free software and open hardware]<br />
<br />
Just another FPGA+microcontroller example: <br />
*[http://melzer.ch/html/body_alya.html The Alya Project] ([http://home.nikocity.de/andymon/hfg/Alya/alya.html old page])<br />
*[http://melzer.ch/ALYA.ASM PIC assembler source code], [http://melzer.ch/ALYA.TDF Altera FPGA code]. Schematic: [http://melzer.ch/Schaltplan1.gif], [http://melzer.ch/Schaltplan2.gif], [http://melzer.ch/Schaltplan3.gif]<br />
<br />
I do not think this means what you think it means... I read "...and a metal programmable (MP) block of 500K gates of digital logic." as meaning that it's a one-time programmable block, more akin to a standard-cell ASIC than an FPGA. This is supported by the fact that their development board contains a separate FPGA chip. Now, granted, having a 500K gate ASIC on board an ARM is a cool thing... but not quite as cool as this chip appeared at first glance.<br />
<br />
===Samsung S3C2443===<br />
*[http://www.samsung.com/global/business/semiconductor/productInfo.do?fmly_id=229&partnum=S3C2443&&ppmi=1427 Samsung S3C2443] Up to 533 MHz, USB 2.0<br />
<br />
==Possible FPGA==<br />
This FPGA is just an example:<br />
*[http://www.xilinx.com/products/silicon_solutions/fpgas/spartan_series/spartan3an_fpgas/capabilities/index.htm Spartan-3AN FPGA Capabilities] Quote: "...Simple and secure embedded application storage with up to 11Mb of integrated user Flash...Enable simple arithmetic and math functions as well as advanced DSP functions to derive over 330 Giga MACs/sec...Up to 32 18 x 18 embedded multipliers support 18-bit signed or 17-bit unsigned multiplication, and can be cascaded to support wider bits..."<br />
**XC3S1400AN-4FGG676CES $91<br />
**XC3S200AN-4FTG256CES $25.87<br />
<br />
====Tool for FPGAs====<br />
*[http://www.xilinx.com/ise/logic_design_prod/webpack.htm xilinx.com: ISE WebPACK is the industry´s only FREE, fully featured front-to-back FPGA design solution for Linux, Windows XP, and Windows Vista]<br />
<br />
===Asynchronous FPGA, AFPGA===<br />
*[http://www.achronix.com/products.html Achronix-ULTRA]<br />
**[http://www.pldesignline.com/news/186700955 Achronix preps 2-GHz Asynchronous FPGA for sampling in 2007]<br />
**[http://vlsi.cornell.edu/fpga.php Asynchronous VLSI and Architecture, Cornell University: Asynchronous Field-Programmable Gate Arrays (AFPGAs)] Quote: "...integrated pipelining support..."<br />
**[http://citeseer.ist.psu.edu/teifel03programmable.html Programmable Asynchronous Pipeline Arrays (2003) John Teifel, Rajit Manohar]<br />
<br />
==Internal Memory==<br />
===RAM===<br />
128MB Dedicated for open files, running software etc., not for storage, or 256MB at all would be really nice and enough for any future software.<br />
<br />
===ROM===<br />
Enough to Hold O/S and a fair number of applications and their settings. Persistent Storage with XIP capability. About 128 MB.<br />
<br />
===Storage===<br />
An internal Micro SDHC should be used for users' files and additional software<br />
<br />
==Wireless data networking==<br />
<br />
===WiMAX support===<br />
[http://en.wikipedia.org/wiki/Wimax WiMAX] is a high-speed data service, similar to wifi, though longer range and newer. Where service is available, this would complement WiFi. Unfortunately, unlike wifi, frequencies vary worldwide, so global usage may be complex.<br />
<br />
===Emerging Protocols===<br />
*[http://en.wikipedia.org/wiki/Near_Field_Communication Near Field Communication] has a few centimeter range, useable for keys, ID badges, pairing bluetooth devices and similar uses. Mentioned in newer bluetooth and SD standards. (No products.)<br />
*[http://en.wikipedia.org/wiki/ZigBee ZigBee] is designed for connecting sensors and switches in buildings, with many options including mesh networks and aggressive power saving compared to bluetooth. (Almost no products available.)<br />
*The [http://en.wikipedia.org/wiki/ANT_%28network%29 ANT network] is for connecting worn devices. Similar to ZigBee, but much simpler and maybe lower power. ([http://www.thisisant.com/?section=9 Short list] of products.)<br />
<br />
==Camera==<br />
<br />
* A camera that can take reasonable quality video and pictures is something many want. Applications vary from simple snapping, to gesture interfaces, video conferencing, barcode reading, buisness card reading, healthcare, servicing, and more.<br />
<br />
* Some people can't take cameras into work - a model without the camera, or some way of removing the camera would be useful or leave the camera chip in place and have a removable lens assembly and replacement backcover.<br />
<br />
* See [[Wishlist:Camera]] for a more detailed wishlist.<br />
<br />
==Display==<br />
===Multitouch screen===<br />
<br />
''Main article: [[Wishlist:Spell_weaving|Spell weaving]]''<br />
<br />
See also [http://pogue.blogs.nytimes.com/2007/03/27/the-multi-touch-screen/ this page] containing a link to a video demonstration.<br />
<br />
A history of multitouch implementations is [http://billbuxton.com/multitouchOverview.html here] ([http://google.com/search?q=cache:billbuxton.com/multitouchOverview.html google cache version])<br />
<br />
*Use examples: [http://www.youtube.com/watch?v=UcKqyn-gUbY&mode=related&search= Multi-touch interface (from Adobe TED)], [http://www.youtube.com/watch?v=1ftJhDBZqss&mode=related&search= Multi Touch (new touchscreen technology)]<br />
<br />
===Bigger and better screen===<br />
2.8" widescreen (like in [http://etencorp.com E-ten] PDA/smartphones), or 3.5" widescreen (like in [http://www.expansys.ie/d.aspx?i=134944 Fujitsu Siemens LOOX N560]).<br />
<br />
262k or 16.7M colurs for displaying images and especially videos.<br />
<br />
OLED for better contrast, more rich colours, and less energy consumption.<br />
<br />
Maybe the [http://www.sharpsme.com/Page.aspx/europe/en/part/LS037V7DW01/ LS037V7DW01] by Sharp could be a solution. It has nearly the same specs as the currently used, but 3,7" -- [[User:Wedge | Wedge]]<br />
<br />
===Distance sensing touchscreen===<br />
{{Main|Hardware:NearlyTouchScreen}}<br />
TouchKo's (now Wacom Company Ltd.) spatial capacitive "touchscreen", can sense fingers at a small distance, so you do not get your display greasy, and can unlike some touchscreens, be operated with gloves.<br />
<br />
===<s>Video acceleration</s>===<br />
Hardware acceleration for video playback and 2D/3D accelleration will be present in [[Neo1973 GTA02]].<br />
<br />
===EPD===<br />
Or electronic paper display, EPD is used in many new devices such as the new Motorola motofone, sonys new e-reader and Irex's iliad. The technology provides thin, lightweight, power saving screens using new eink technology. This technology could cut the weight of the phone and its power usage. For more info see: [http://www.eink.com eink's website].<br />
<br />
Pro: laserprinter like quality, glossy, very stable image, easy on the eyes. Electronics are similar to TFT. Very low power consumption. <br />
<br />
Con: Black and grey only (like a newspaper, but glossy), although there were already color prototypes in 2005. low framerate (5fps). Can reflect light (like paper), backlight is impossible.<br />
<br />
===Transreflective===<br />
It would be nice to have (the option of) a transreflective display, which while being less bright, is readable without needing to power the backlight. Then again, it depends on how much power the backlight uses compared to everything else...<br />
<br />
==="Slightly" Larger Screen===<br />
43mm x 57mm (2.8inch diagonal) is tiny. A 53mm x 71mm (3.5 inch diagonal) like on the TD035STEE1 would be a nice improvement. A widescreen format at about 53mm x 82.5mm instead of the 3:4 aspect ratio would be even cooler (if one could be found).<br />
<br />
===Second Display===<br />
A 32x32 OLED display possibly on the back for camera framing or on an edge so it can be viewed like a pager.<br />
This could be used to display any number of alerts (from any installed software) the alerts could have a dynamic prioritisation which means during the work day a message from the boss has high priority but lower at home (could be GPS/Time controlled?) multiple alerts shrink the icons to a 3x3 grid higher priority messages get more space.<br />
<br />
===Micro Projector===<br />
[http://www.engadget.com/media/2006/02/digismartphone2.jpg Like the one shown here], new cellphones are now coming out with a small, low power projector. This can be used to show movies from your cell phone with 0.5m high image on a while wall for example...<br />
<br />
==Input devices==<br />
<br />
===No Dependence on Stylus===<br />
The Neo's basic functionality should be completely usable without a stylus, Like the iPhone but with stylus use for precision work.<br />
<br />
===A laser projection keyboard===<br />
Similar to [http://www.thinkgeek.com/computing/input/8193/ this], except the device would be integrated into the phone itself. Setting the Neo up on a stand on a flat surface (perhaps a stand could be built into the back of the Neo itself, or into a case) would turn the Neo into a micro-laptop. There may be several issues with the inclusion of this technology, including patents, the space required to project the laser grids, and the power consumption. If possible, however, it would make text input a breeze.<br />
<br />
===Just a few more Buttons===<br />
<br />
2 buttons more, 3 buttons total, mounted sideways would be enough. You could use them for play/pause and loudness controll while the phone remains in your pocket (display locked, ...), reading mails, rss, ebooks,... without wasting display space and so on.<br />
<br />
With 5 buttons in total you could possibly emulate a keyboard (2^5 = 32 combinations) for those who know how to play a flute. Useable onehanded, not wasting display space and faster than t9. (It's not faster than T9 - I've used this system with the microwriter agenda --[[User:Speedevil|Speedevil]] 00:00, 2 July 2007 (CEST)) Hopefully this is not patented already.<br />
<br />
===D-Pad and Buttons===<br />
*Adding a D-pad (to the bottom of the phone) and 2 to 4 buttons (to the top) would provide some tactile input controls, in addition to the touchscreen. They could be used as shortcut keys in the menu, or playback control when playing media. When the phone is held sideways, they can be used as games controls. (With touchscreen alone, gameplay options are limited)<br />
<br />
Game buttons would be best on both sides of the screen. The larger the buttons, the better. 2x 4 buttons in up-down-left-right configuration + some extra buttons separately a bit lower on the device would be good for many for emulation games. <br />
<br />
Here is a concept drawing of a possible neo1973 gaming version: <br />
(This has a 4-way direction pad, 8 way may be better for gaming)<br />
<br/><br />
[[Image:Neogame90.jpg]]<br />
<br/><br />
Shoulder buttons would be a great addition, too. It would be interesting if there was a total 4 of them, one for every corner. It would make the phone very flexible for rotating and 2 to 6 players playing on one device.<br />
<br/><br />
:''Note'' : The [http://en.wikipedia.org/wiki/Tapwave_Zodiac Tapwave Zodiac] Palm PDA / Game console hybrid had a similar setup - with an analog stick on the left (also used for quick selection using a radial main menu when working as a PDA), 4 buttons on the right (also configurable for shortcuts when using the device as PDA), and 2 shoulder buttons. Also it had and still has an enthusiastic scene of homebrew development (almost any console emulator for PalmOS can also take advantage of the additional buttons and graphic power of the device). If we also take into account the success encountered by the [http://en.wikipedia.org/wiki/GP32 GP32] in the past and the [http://en.wikipedia.org/wiki/GP2X GP2X] currently on the homebrew scene, it's not unreasonable to plan a future OpenMoko device with both a SmartPhone/PDA functionnality ''and'' hand-held console targeting homebrew development.<br />
<br />
===Thumb keyboard or keyboard attachment accessory===<br />
*Could be slide out or clamshell (hinge on long side) design with an external OLED. The keyboard should be protected when not in use.<br />
*Could be a clip on keyboard that attaches to the serial port or communicates by bluetooth (not preferred for permanent keyboard users).<br />
*Cheap clippable miniusb keyboard<br />
*One of the layouts proposed in [[Hardware:Keyboards]]<br />
* What about virtual keyboard? [[http://www.extremetech.com/article2/0,3973,539778,00.asp Keyboard]]<br />
<br />
===Analogue Controllers===<br />
<br />
====Trackball====<br />
A trackball would provide an efficient mouse-like interface in a very compact package. As exemplified in the newer Blackberry&reg; models.<br />
Maybe instead an optical sensor as are used in mice could be used so that the whole phone can be moved over a surface just like a mouse. (It could function as a Bluetooth mouse for other devices like laptop computers: see [[Bluetooth_Support#Acting_as_HID_device]]. Adding one other two-axis analogue input (possibly just the screen) would make the Neo usable as a TrackPoint or scroll-and-tilt mouse.) The same sensor might be usable as a barcode reader.<br />
<br />
====Analog Joystick====<br />
A joystick, or [http://www.extremetech.com/article2/0,1697,1772689,00.asp Rollermouse]-like device would provide additional control, compared with touchscreen only.<br />
*A standard [http://en.wikipedia.org/wiki/Pointing_stick pointing stick (ie. TrackPoint)] might serve well. As a fairly standard part, might they be quite inexpensive?<br />
<br />
====Dual analogues====<br />
Dual analogue controllers (one trackball or joystick above, one below the screen, most likely) might even be feasible. That might be overkill since the accelerometers or touchscreen can be used to provide a second analogue input. But it would be nice to have four axes of analogue control without having to tilt the screen away from you or partly cover it with your hand.<br />
<br />
===TV/radio receiver===<br />
[[Digital Television]], [[Digital Radio]] or even normal analogue TV/radio is widely available in the world, though unfortunately in various different forms. In markets where one standard is widespread, and hardware is suitable, it would be a great extension of the phone to a general entertainment device for when you're away from home. Multi standard devices would be ideal, but may not be small, low-power, or cheap.<br />
A good start would be an FM tuner, since it's one of the most widely used formats of radio broadcasting in the world.<br />
<br />
Here's a selection of chips, though it's not clear if the drivers are open source. http://www.sigmatel.com/products/portable/wireless/fmtuner.aspx#fragment-14<br />
http://www.st.com/stonline/products/families/automotive/am_fm_tuners.htm<br />
<br />
===Accelerometer=== <br />
This enables the phone to sense which direction 'down' is, and to sense any movements the phone makes.<br />
<br />
See [[Accelerometer Fundamentals]] for more information on accelerometers as they may be used in phones.<br />
<br />
In some cases integrated gyroscopes may also be needed. A [[#Digital compass]] can even be of more use since it gives absolute rotation so slow rotations could also be measured. A 3D compass would be nicest, but a simple 2D compass already is a helpful addition to the accelerometers.<br />
<br />
*[[Wishlist:3D Viewport|3D Viewport]]<br />
*[[Wishlist:Computer Mouse|Computer Mouse]]<br />
*[[Wishlist:Determine Position|Determine Position]]<br />
*[[Wishlist:Dynamic Screen Orientation|Dynamic Screen Orientation]]<br />
*Change media player playlist when jogging vs walking. <br />
*Attempt to use to stabilise any future camera.<br />
<br />
This feature is scheduled for inclusion in the phase 2 Neo1973, currently slated for release in October 2007.<br />
<br />
===Side-Mounted Touch Strip===<br />
Add a "touch strip" sensor onto the side of the phone which can be used to scroll. By having it on the side you can use your thumb to scroll comfortably while holding the phone one-handed. An 8-element capacitive sensor would work wonderfully and be easy to fab using either a Quantum QT411 (http://www.qprox.com/products/qslide_qt411.php) or Analog Devices AD7143 (http://www.analog.com/en/prod/0,2877,AD7143,00.html) controller. The Analog Devices chip seems better suited due to it's smaller allowable element size.<br />
*With the AD7143 you can have an 8-element (128-position) 25mm long strip - Perfect!.<br />
*With a few OLED screens beneath the strip it could be used as dynamic configurable buttons/alerts eg. zoom/flash/shutter with a camera application and SMS/Email/Voicemail alerts in standby<br />
<br />
<br />
:Maybe it would be also possible to use is as finger print reader? --[[User:Tolein|tolein]] 20:18, 1 October 2007 (GMT+1)<br />
<br />
===Heart Rate Compatibility=== <br />
<br />
An RF interface to receive data from popular heart rate straps (Polar, Garmin, Sigma, Suunto, etc.). This would go along well with the existing GPS functionality and possible future Accelerometer functionality to make for a full-blown workout tool.<br />
<br />
Software can be written to track heart rate along a running, cycling, skiing, swimming loop, to monitor max and min heart rate, to match heart rate data to GPS coordinates and print map data w/ relevant data.<br />
<br />
===Digital compass=== <br />
A digital compass is useful for orienting maps to the terrain and other location/direction/orientation based applications (... is 300 meter that way) when the user is standing still (regardless of GPS reception) and for following a bearing when GPS reception is poor or speed is low. Also could be used to make the accelerometer data more exact.<br />
<br />
Very small [[I2C]] sensors like [http://www.ssec.honeywell.com/magnetic/hmc6352.html Honeywell's HMC6352 2-Axis Digital Integrated Compass] (6.5 x 6.5 x 1.5 mm) are very appropriate for this.<br />
<br />
*[[Wishlist:Auto Align Map]]<br />
<br />
See [[Wishlist - Hardware: Digital compass]] for more information<br />
<br />
===Thermometer===<br />
An electronic thermometer might become handy for some users.<br />
<br />
There are very small [[I2C]] devices available, that could easily integrate to the existing bus. For example [http://focus.ti.com/docs/prod/folders/print/tmp100.html this one from ti].<br />
(Could just be cheap and use the thermometer from the battery, thats how they did it in the nokia 5140's). Also is integrated in a barometer/altimeter like the SMD500 mentioned in [[Wish List - Hardware - Atmospheric]].<br />
<br />
===Barometer and Variometer (Altimeter)===<br />
<br />
A Barometer measures air pressure. This can be used to give weather information, and also as a variometer, to sense relative altitude. Variometers are commonly used in flying microlight and ultralight aircraft, to get accurate relative altitude.<br />
<br />
These are also common on high end GPS units. This is a great feature for walkers as you can tell how far you have got on any accent/decent.<br />
<br />
See [[Wish List - Hardware - Atmospheric]] for more information.<br />
<br />
===Finger print sensor===<br />
A fingerprint sensor gives easy and fast access to the phone, could lock the touchscreen etc. An example of this device can be found at [http://www.sonystyle.com/is-bin/INTERSHOP.enfinity/eCS/Store/en/-/USD/SY_BrowseCatalog-Start?CategoryName=cpu_VAIONotebookComputers_UX_Series&Dept=computers Sony UX17].<br />
<br />
Most fingerprint sensors in the embedded market include a navigation mode, where they work similar to either a touch-stick or touch-pad of a laptop.<br />
<br />
===Barcode Scanner===<br />
*less cpu intensive and more reliable than camera+ocr<br />
*though, bluetooth-enabled readers are already available.<br />
<br />
===Light Sensor===<br />
Ability to sense ambient light, and act accordingly. i.e if it's 3am and LightValue<.1 then Ring Quietly.<br />
<br />
===Wheel===<br />
A navigation wheel like on a sony/ericsson 810i would be nice.<br />
<br />
===Proximity Sensor===<br />
Switch off backlight when you place the phone to your ear. Prevent accidental activation of speakerphone or other sounds when the phone is near the ear (prevent hearing damage). Possibly switch the speakerphone on or off automatically depending on if the phone is by your head or not.<br />
<br />
=== Make ''all'' unlocking of phone, password protected===<br />
<br />
When my (current non-neophone) phone is in my pocket and I have it locked, it sometimes accidentally unlocks itself since only two keystrokes in the correct order are necessary to unlock it. When it's unlocked and still in my pocket it sometimes calls someone without my knowledge. All phones I've seen today have a press-just-one-button bypass to answer an incoming call even when the phone is locked. I suggest making the locking mechanism let the user configure it so that the user has to enter a password even for answering incoming calls. The likeliness of the phone accidentally runbbing against my car keys, hitting a ten character long password, unlocking the phone without my knowledge and consent is low enough even for us most unlucky users.<br />
<br />
==Expansion==<br />
===Positioning of Buttons, Connections and ports===<br />
<br />
Ideally any cable ports such as charging, USB, audio, docking should not get in the way of your hand or fingers when holding it in it's normal orientation. For the sake of SDIO cards an external SD slot should be on the top edge. IR for remote control software and ease of inter-device communication should be on the corner so that it is facing away from you for both orientations. Buttons obviously are positioned for finger control. An example of how '''not''' to do this would be the HTC Universal<br />
<br />
===Storage===<br />
<br />
====MMC/SD/SDIO slot (rather than?) miniSD or microSD====<br />
*Cheaper, more durable cards in a widely accepted format.<br />
*Much much larger storage capacity, [http://blog.scifi.com/tech/archives/2007/08/23/toshiba_unleash_1.html even 32GB]<br />
*Cards are harder to lose<br />
*Wider selection of accessories, including SDIO accessories.<br />
*Make externally available so that larger length SDIO cards can be used (thinking about SDIO WLAN here)<br />
*[http://en.wikipedia.org/wiki/Secure_Digital_card#SDHC SDHC] compatible. It seems to already have the right hardware for it - see [[Neo1973_Hardware#microSD-Card]].<br />
<br />
====Two SD slots====<br />
*Micro SDHC for /home partition. Keep like current design underneath SIM card<br />
*Hot swappable externally accessible normal size SDHC/SDIO slot<br />
<br />
===Local Communication===<br />
<br />
====USB====<br />
* 5V Powered, to avoid having to carry around a hub for when you want to occasionally plug in a memory stick. Many powered hubs will not recognize a totally unpowered host. Provide a maximum current to drive a basic USB keyboard/memory stick/mouse/webcam/astrowebcam. This could be done by adding a small cheap power converter like the [http://www.national.com/pf/LM/LM2753.html LM2753]<br />
* USB 2.0 <br />
* Standard type A socket for quick & easy insertion of memory sticks etc.<br />
* OTG (is this maybe supported already ?)<br />
* Bootable USB device emulation: the possibility to boot any computer on a bootable flagged partition of the transflash.<br />
* Protection against incorrectly wired USB ports: some USB ports are wired incorrectly; if the +5V and GND are swapped, the device would get -5V when it's expecting +5V, which could burn some chips. A reverse-biased diode between +5V and GND, D+ and GND, D- and GND, and (if used) ID and GND, with a low enough forward voltage drop (to limite the negative voltages to what the chips can withstand), would protect the device by tripping the port's short circuit protection.<br />
<br />
====Wireless USB support====<br />
[http://en.wikipedia.org/wiki/Wireless_USB Wireless USB] is the wireless version of USB offering data-rates up to 480 Mbit/s over short distances (<3 meter). Chipsets suitable for a phone are likely to take some time to be available.<br />
<br />
====SIR/FIR transceiver (Serial Infrared) / IR remote control====<br />
*An infrared transceiver is cheap, small, and useful for sync with many laptops and mobile phones. <br />
*Replace/emulate all IR-based remote controls used for your tv, vcr, etc on your neo cell phone.<br />
** replaces multiple 'dumb' devices with a single intelligent device (your neo) that you will probably carry with you at all times anyway. <br />
**Command sets should be retrieved from a database or learned from other less intelligent remote control devices with macros. <br />
**reduces clutter, particularly in the living room.<br />
**inceases the neo's practical status as an 'always-have' device. <br />
<br />
Other uses.<br />
*Detecting reflections from inside of a caddy, and switching from active mode.<br />
*FIR would be a nice option, as it's some 40 times faster than SIR.<br />
<br />
===Other===<br />
<br />
====Video Out====<br />
*Through a docking port<br />
**S-Video/Composite Out<br />
**DVI Out<br />
<br />
==Output devices==<br />
<br />
===LED===<br />
*The Neo1973 GTA02 will have LEDs of some sort behind at least one button. [http://lists.openmoko.org/pipermail/community/2007-July/008458.html]<br />
*A blinking LED would be a cheap, low power way to inform the user of new SMS/Email....<br />
**An alternative to this would be for one small part of the LCD to be separately backlit.<br />
**This requires the CPU and LCD to be somewhat active, to keep the LCD refreshed, but gives much more information.<br />
**A Small OLED Screen could be used and display much more information than a LED with minimal power usage.<br />
<br />
*For example a multicolor LED which pulses yellow for GSM/GPRS transmit, blue for Bluetooth/Wifi, green to indicate non-urgent information - missed call etc, red to indicate battery low or other urgent notices.<br />
<br />
**The LED and button ideas could be combined: illuminated buttons.<br />
**It must be possible to completely disable the LED to save power or other personal preferences.<br />
<br />
=== Flashlight ===<br />
For finding keys, or any other application. May also optionally pulse in time with ring, to make phone more visible.<br />
This is really well done in Nokia 5500.<br />
<br />
=== FM transmitter ===<br />
Small FM transmitter to output to car, and other nearby radios.<br />
<br />
===HAC Compliance===<br />
[http://quux.wiki.zoho.com/WhereAreHACphones.html Here] is some summary/discussion of how hearing aid compliance rules work in the US. Specifically it would be nice to see the phone include a [http://www.hearingresearch.org/Dr.Ross/telecoil_and_telephones.htm telecoil], which allows the phone to connect wirelessly to many standard hearing aids.<br />
<br />
==Mobile Communication options==<br />
<br />
===Generic Access Network / Unlicensed Mobile Access===<br />
This technology requires cooperation from the cellular provider, but [http://en.wikipedia.org/wiki/Unlicensed_Mobile_Access UMA/GAN] is already offered by T-Mobile in the United States, and perhaps others in other countries. Allowing the user to roam from GSM to wifi, this technology can save the end user a significant amount of money, and also allow the user to deploy coverage where there was none before. There are only a few UMA capable phones currently, but it would be great if this could be made to work on a phase 2 type OpenMoko device.<br />
<br />
Note that this features requires a more advanced access to the GSM modem. Special messages needs to be exchanged with the network.<br />
<br />
===Faster/better mobile connectivity.===<br />
[http://en.wikipedia.org/wiki/Gsm GSM]/[http://en.wikipedia.org/wiki/GPRS GPRS] is at best slow. An incremental improvement would be a radio with [http://en.wikipedia.org/wiki/EDGE EDGE ] support. EDGE is an evolved GSM standard and, like GPRS, it operates on the same frequency as voice. This means a quad-band EDGE radio will have near-complete worldwide coverage. <br />
<br />
[http://en.wikipedia.org/wiki/UMTS UMTS] - which is widespread in Europe and being deployed in the US, [http://en.wikipedia.org/wiki/HSDPA HSDPA] (asia) and any other mobile standards would be nice for faster data connectivity and coverage.<br />
It is unlikely that all of these will be supported initially, but it is a goal. These faster standards operate in different frequencies from GSM/GPRS/EDGE. Which frequency exactly will depend on the carrier and country. For UMTS in the US, AT&T uses 850/1900 MHz but T-Mobile will use 2100/1700 MHz for example.<br />
<br />
Until that goal is reached, it is likely that some phones will be brought out for various specific markets - Europe, Asia, US.<br />
<br />
===Ability to use multiple SIMs/networks===<br />
* External SIM sockets are widely available in China, a dual external socket would be a very good solution.<br />
* [http://www.fonefunshop.co.uk/dualsim/digital.htm Dual SIM card kit] - two SIMs are trimmed and combined, software supportwould be needed, and both can't be used at once...<br />
* Some networks support multiple numbers on one SIM. Unfortunately this won't allow split networks.<br />
* A second/dual GSM module would allow full use of both sims at all times.<br />
* As a hack, [http://wiki.openmoko.org/wiki/Wish_List#Bluetooth_powered_Multi-SIM_support use another mobile via BT].<br />
** As many as three SIM slots would be genuinely useful, especially for a 3G phone - some 3G data tariffs are only available on data-only SIMs. A user could quite reasonably have one SIM for data, once SIM for his personal voice calls, and a third SIM for his business number.<br />
<br />
===PMR446/FRS Radio===<br />
* Include a PMR/FRS Radio.<br />
* A two-way walkie talkie lets you use the phone to communicate with friends without requiring a GSM connection (crowded networks at festivals, at locations with no GSM coverage).<br />
<br />
===[[DECT]]===<br />
* Include a [[DECT]] GAP/CAT-iq transceiver so you can use your home and/or office PSTN line<br />
** Ability to use Alcatel phonebook stuff (like provided by the eventphone.de phone equipment) would be very nice too<br />
<br />
===[[SIP phone]]===<br />
Make stripped down (and thus cheaper) version of the Neo1973 phone for use as a SIP phone. Remove GPS, GSM, accelerometers, stilus.<br />
<br />
Addition of an centimeters-precise location system [http://en.wikipedia.org/wiki/Real_Time_Location_Systems RTLS] would be nice, as it will allow highly sensible indoor context detection. Image to put the phone next to your mirror (where you shave daily) and observe it automatically switch to news radio channel. Or put it next to your bed and see it automatically switch to "sleeping" mode, when only calls from predefined numbers are accepted.<br />
<br />
=='''Casing'''==<br />
See also: [[Alternate Neo1973 case designs]] for a list of cases being considered for design/manufacture by the community.<br />
<br />
=== Expansion Back Casing ===<br />
Replacement backs with additional features ranging from solar power, larger batteries, extra hardware, ...<br />
<br />
===[[Expansion Front Casing|Expansion Front Casing]]===<br />
Replacement fronts with e.g. extra buttons.<br />
<br />
=== Space efficient Lanyard ===<br />
The hole at the bottom of the phone takes a lot of space. A [http://en.wikipedia.org/wiki/Kensington_Security_Slot Kensington Security Slot] could be used instead.<br />
<br />
=== Rugged version ===<br />
We need something you can drop from 4 feet in to a puddle of dirty water on construction site. Sunlight readable display. The big ugly pseudo military version.<br />
<br />
=== Transparent ===<br />
Make a transparent, see-through casing. Why do we need a closed casing for open hardware and open software? Show the world it is a truly Free/Open source phone.<br />
<br />
=== Blank ===<br />
Even though the transparent case would work too, I would like to see a blank case of pure black or white so people could have the option of air-brushing,painting or even drawing on the case.<br />
<br />
==Misc==<br />
===Galileo/GLONASS/GPS receiver===<br />
*A multi-standard satellite positioning module would be nice eventually, it does not seem to be near-term due to chipset availability problems. Galileo is the to be launched (2011) European positioning system. GLONASS is the already existing Russian one.<br />
<br />
===X10 RF Remote===<br />
Many PC-based media centers are being equipped with an RF (433 MHz) / X10-based remote control. The [http://en.wikipedia.org/wiki/X10_(industry_standard) X10] protocol also facilitates home automation to control lamps, switches, etc.<br />
The advantages of using RF for control instead of Infra-red this that it also works when furniture, walls, or doors are blocking the path between RF remote and the equipment or device. [http://www.lirc.org/ Lirc] supports X10-based RF remotes (but expects having an USB RF receiver attached to the media center).<br />
<br />
===RFID tag/RFID Reader===<br />
* Implementation/Cooperation with: [http://www.rfidguardian.org/ RFID-Guardian]<br />
*An enable-able tag would be of use - for example being able to use the phone to open doors, or cars. Unfortunately, it's moderately hard to do secure programmable tags that are compatible with existing systems, for obvious reasons.<br />
* Say you have RFID tags on your personal belongings: cellphone, keys... Neo could be programmed to remember the last recorded GPS location before it lost contact with the respective RFIDs. It'd be trivial to check where you left your cellphone, get directions from a map...or beep when the phone gets out of RFID range.<br />
===NFC chip===<br />
*A Near Field Communication chip, with this chip it will be possible to pay with your phone (like a credit card)in the near future, see [http://www.nokia.com/A4305081 Nokia]for details<br />
*NXP is a chip fabricator which provides NFC chips [http://nxp.com NXP] direct link>> www.nxp.com/#/pip/cb=[type=product,path=/53420/53424]|pip=[pfp=53424][0] their chips also support the above RFID reading<br />
<br />
===Less weight===<br />
* Work on the weight of the Neo1973 and following devices. At the present time the Neo1973 is just a moderate / normal business or multimedia phone. The ordinary "user" may want something lighter. Take a look at the following table, that's the Neo1973 compared with other common bussiness or multimedia phones.<br />
{|border="1"<br />
| Neo1973 || Fujitsu-Siemens LOOX N560 || E-Ten Glofiish X500+ || Sony Ericsson P990i || iPhone || Nokia E65 <br />
|- <br />
| 184 g || 160 g || 146 g || 150 g || 135 g || 115 g <br />
|-<br />
|}<br />
<br />
===Make it smaller===<br />
* To stay within physical matters: Maybe the Neo1973 is also just a normal business/multimedia phone when looking at the size. It would be great the shrink it a bit. Especially the thickness of 18.5 mm could be worked on!<br />
<br />
===Standard 3.5mm headphone jack===<br />
The Neo1973 uses a 4-conductor 2.5mm jack for stereo headphones and a microphone. A 2.5mm jack is the most common for headsets. <br />
<br />
There is an emerging convention used in the Nokia N800 and some other devices. A 4-conductor 3.5mm jack that can use a microphone with special headsets, but can also be used with off-the-shelf 3.5mm stereo headphones. Adapters to 2.5mm are of course available and this 3.5mm jack is much more robust.<br />
<br />
Neglecting space limitations, multiple sockets - 2.5mm and 3.5mm would be nice. Probably not practical in a phone. Other expanded plugs might allow remote controls.<br />
<br />
Other uses might be better met using bluetooth, or USB audio.<br />
<br />
===Laser Pointer===<br />
Include a built in laser pointer. Everything is better with lasers.<br />
<br />
===Completely free hardware===<br />
Consider selling one device with absolutely no non-free components in it, even if that means dropping the GSM support. I believe having one such device available would be good, because then it could be recommended by organizations like the FSF which typically never recommends anything if it has even a little non-free code in it.<br />
<br />
=== Consider economy / inexpensive / less featured edition ===<br />
Some people want less features, because they do not need them. Leaving out some features either lets the phone get smaller or possibly enhances battery live.<br />
<br />
One big suggestion in this area is a b/w lower res display instead of the big color display.<br />
<br />
=== Inductive Charger ===<br />
<br />
It would be nice if it was possible to charge the phone without having to connect a cable. I'd like to have a simple docking station with an inductive charger like the type that's used for electric toothbrushes [http://home.howstuffworks.com/question292.htm ]. The charger itself could get its power from a standard wall-wart power supply, or it could be USB/Firewire powered.<br />
<br />
==Related Hardware==<br />
See [[Related Hardware]]<br />
<br />
[[Category:Hardware ideas| ]]<br />
[[Category:User]]</div>Bashttp://openmoko.org/wiki/Wish_List_-_HardwareWish List - Hardware2007-10-11T09:11:43Z<p>Bas: /* TV/radio receiver */</p>
<hr />
<div>This page details hardware features which some would like to go into future phones similar to the [[Neo1973]].<br />
<br />
Related pages are:<br />
*[[Wishlist - Hardware - Novel Devices]] - openmoko will run on a large number of devices in the future, some of which may be DVD players, cameras, or convergance devices. <br />
*[[Wishlist:Unlikely]] - Hardware that is unlikely to appear in any OpenMoko device, due to it being impossible to fabricate with near-term technology, or for other reasons.<br />
*[[Wishlist:Accessories]] - Accessories that people would like, that connect easily to the phone - initially primarily for the Neo1973 <br />
*[[Wishlist:Expansion]] - add-ons to the phone, maybe involving hardware changes, and software and hardware protocols to implement these.<br />
<br />
This page is rather long. Before adding a new idea, please read through this page and the above pages, to make sure your idea has not been suggested before.<br />
<br />
==Processor==<br />
===AT91CAP9S500A (ARM9 + FPGA-port)===<br />
Why FPGA?:<br />
*[http://hardware.silicon.com/servers/0,39024647,39166443,00.htm?r=1 20 March 2007 Green supercomputer is 'go' in Scotland] Quote: "...A supercomputer 10 times more energy efficient and up to 300 times faster than its traditional equivalents..."<br />
<br />
Take a look at this microcontroller, that integrates an ARM9 microcontroller and a dedicated FPGA port: AT91CAP9S500A. It has "only" a max. clock at 200MHz, but can use a FPGA for hardware acceleration, that could be used for video (de)compression, [http://en.wikipedia.org/wiki/AacPlus_v2 aacPlus v2]/[http://en.wikipedia.org/wiki/HE-AAC_v2 HE-AAC v2] sound (de)compression and many other things. HE-AAC v2 is better than [http://en.wikipedia.org/wiki/MP3 MP3].<br />
*[http://www.atmel.com/dyn/products/product_card.asp?family_id=689&family_name=AT91CAP+Microcontrollers&part_id=4137 AT91CAP9S500A] Quote: "...The AT91CAP9S500A is built around a 12-layer bus matrix, allowing a maximum internal bandwidth of twelve 32-bit buses. Its distributed DMA architecture enables multiple data transfers to take place between the processor, memories and peripherals with minimal processor overhead...".<br />
*[http://www.atmel.com/dyn/resources/prod_documents/doc6310.pdf GNU-Based Software Development on AT91SAM Microcontrollers]<br />
*Maybe this is a good tool?: [http://www.jhdl.org/ BYU JHDL, Open Source FPGA CAD Tools]<br />
*[http://www.eetimes.com/showArticle.jhtml;?articleID=197002705 02/05/2007, FPGA tool bottleneck stalls HPC] Quote: "...Current FPGA synthesis, placement and routing tools are written for hardware designers, not software programmers simply trying to accelerate an algorithm..."<br />
<br />
This seems to be a good hardware mix (ARM+FPGA). It does [http://en.wikipedia.org/wiki/Theora Ogg Theora] or [http://en.wikipedia.org/wiki/MJPEG MJPEG] in the FPGA with 1 million gates:<br />
*http://sourceforge.net/projects/elphel, [http://wiki.elphel.com/index.php?title=10353 board 10353], [http://wiki.elphel.com/index.php?title=Camera_hardware camera hardware], [http://wiki.elphel.com/index.php?title=Main_Page Main page], [http://www.elphel.com/articles/index.html Imaging solutions with Free software and open hardware]<br />
<br />
Just another FPGA+microcontroller example: <br />
*[http://melzer.ch/html/body_alya.html The Alya Project] ([http://home.nikocity.de/andymon/hfg/Alya/alya.html old page])<br />
*[http://melzer.ch/ALYA.ASM PIC assembler source code], [http://melzer.ch/ALYA.TDF Altera FPGA code]. Schematic: [http://melzer.ch/Schaltplan1.gif], [http://melzer.ch/Schaltplan2.gif], [http://melzer.ch/Schaltplan3.gif]<br />
<br />
I do not think this means what you think it means... I read "...and a metal programmable (MP) block of 500K gates of digital logic." as meaning that it's a one-time programmable block, more akin to a standard-cell ASIC than an FPGA. This is supported by the fact that their development board contains a separate FPGA chip. Now, granted, having a 500K gate ASIC on board an ARM is a cool thing... but not quite as cool as this chip appeared at first glance.<br />
<br />
===Samsung S3C2443===<br />
*[http://www.samsung.com/global/business/semiconductor/productInfo.do?fmly_id=229&partnum=S3C2443&&ppmi=1427 Samsung S3C2443] Up to 533 MHz, USB 2.0<br />
<br />
==Possible FPGA==<br />
This FPGA is just an example:<br />
*[http://www.xilinx.com/products/silicon_solutions/fpgas/spartan_series/spartan3an_fpgas/capabilities/index.htm Spartan-3AN FPGA Capabilities] Quote: "...Simple and secure embedded application storage with up to 11Mb of integrated user Flash...Enable simple arithmetic and math functions as well as advanced DSP functions to derive over 330 Giga MACs/sec...Up to 32 18 x 18 embedded multipliers support 18-bit signed or 17-bit unsigned multiplication, and can be cascaded to support wider bits..."<br />
**XC3S1400AN-4FGG676CES $91<br />
**XC3S200AN-4FTG256CES $25.87<br />
<br />
====Tool for FPGAs====<br />
*[http://www.xilinx.com/ise/logic_design_prod/webpack.htm xilinx.com: ISE WebPACK is the industry´s only FREE, fully featured front-to-back FPGA design solution for Linux, Windows XP, and Windows Vista]<br />
<br />
===Asynchronous FPGA, AFPGA===<br />
*[http://www.achronix.com/products.html Achronix-ULTRA]<br />
**[http://www.pldesignline.com/news/186700955 Achronix preps 2-GHz Asynchronous FPGA for sampling in 2007]<br />
**[http://vlsi.cornell.edu/fpga.php Asynchronous VLSI and Architecture, Cornell University: Asynchronous Field-Programmable Gate Arrays (AFPGAs)] Quote: "...integrated pipelining support..."<br />
**[http://citeseer.ist.psu.edu/teifel03programmable.html Programmable Asynchronous Pipeline Arrays (2003) John Teifel, Rajit Manohar]<br />
<br />
==Internal Memory==<br />
===RAM===<br />
128MB Dedicated for open files, running software etc., not for storage, or 256MB at all would be really nice and enough for any future software.<br />
<br />
===ROM===<br />
Enough to Hold O/S and a fair number of applications and their settings. Persistent Storage with XIP capability. About 128 MB.<br />
<br />
===Storage===<br />
An internal Micro SDHC should be used for users' files and additional software<br />
<br />
==Wireless data networking==<br />
<br />
===WiMAX support===<br />
[http://en.wikipedia.org/wiki/Wimax WiMAX] is a high-speed data service, similar to wifi, though longer range and newer. Where service is available, this would complement WiFi. Unfortunately, unlike wifi, frequencies vary worldwide, so global usage may be complex.<br />
<br />
===Emerging Protocols===<br />
*[http://en.wikipedia.org/wiki/Near_Field_Communication Near Field Communication] has a few centimeter range, useable for keys, ID badges, pairing bluetooth devices and similar uses. Mentioned in newer bluetooth and SD standards. (No products.)<br />
*[http://en.wikipedia.org/wiki/ZigBee ZigBee] is designed for connecting sensors and switches in buildings, with many options including mesh networks and aggressive power saving compared to bluetooth. (Almost no products available.)<br />
*The [http://en.wikipedia.org/wiki/ANT_%28network%29 ANT network] is for connecting worn devices. Similar to ZigBee, but much simpler and maybe lower power. ([http://www.thisisant.com/?section=9 Short list] of products.)<br />
<br />
==Camera==<br />
<br />
* A camera that can take reasonable quality video and pictures is something many want. Applications vary from simple snapping, to gesture interfaces, video conferencing, barcode reading, buisness card reading, healthcare, servicing, and more.<br />
<br />
* Some people can't take cameras into work - a model without the camera, or some way of removing the camera would be useful or leave the camera chip in place and have a removable lens assembly and replacement backcover.<br />
<br />
* See [[Wishlist:Camera]] for a more detailed wishlist.<br />
<br />
==Display==<br />
===Multitouch screen===<br />
<br />
''Main article: [[Wishlist:Spell_weaving|Spell weaving]]''<br />
<br />
See also [http://pogue.blogs.nytimes.com/2007/03/27/the-multi-touch-screen/ this page] containing a link to a video demonstration.<br />
<br />
A history of multitouch implementations is [http://billbuxton.com/multitouchOverview.html here] ([http://google.com/search?q=cache:billbuxton.com/multitouchOverview.html google cache version])<br />
<br />
*Use examples: [http://www.youtube.com/watch?v=UcKqyn-gUbY&mode=related&search= Multi-touch interface (from Adobe TED)], [http://www.youtube.com/watch?v=1ftJhDBZqss&mode=related&search= Multi Touch (new touchscreen technology)]<br />
<br />
===Bigger and better screen===<br />
2.8" widescreen (like in [http://etencorp.com E-ten] PDA/smartphones), or 3.5" widescreen (like in [http://www.expansys.ie/d.aspx?i=134944 Fujitsu Siemens LOOX N560]).<br />
<br />
262k or 16.7M colurs for displaying images and especially videos.<br />
<br />
OLED for better contrast, more rich colours, and less energy consumption.<br />
<br />
Maybe the [http://www.sharpsme.com/Page.aspx/europe/en/part/LS037V7DW01/ LS037V7DW01] by Sharp could be a solution. It has nearly the same specs as the currently used, but 3,7" -- [[User:Wedge | Wedge]]<br />
<br />
===Distance sensing touchscreen===<br />
{{Main|Hardware:NearlyTouchScreen}}<br />
TouchKo's (now Wacom Company Ltd.) spatial capacitive "touchscreen", can sense fingers at a small distance, so you do not get your display greasy, and can unlike some touchscreens, be operated with gloves.<br />
<br />
===<s>Video acceleration</s>===<br />
Hardware acceleration for video playback and 2D/3D accelleration will be present in [[Neo1973 GTA02]].<br />
<br />
===EPD===<br />
Or electronic paper display, EPD is used in many new devices such as the new Motorola motofone, sonys new e-reader and Irex's iliad. The technology provides thin, lightweight, power saving screens using new eink technology. This technology could cut the weight of the phone and its power usage. For more info see: [http://www.eink.com eink's website].<br />
<br />
Pro: laserprinter like quality, glossy, very stable image, easy on the eyes. Electronics are similar to TFT. Very low power consumption. <br />
<br />
Con: Black and grey only (like a newspaper, but glossy), although there were already color prototypes in 2005. low framerate (5fps). Can reflect light (like paper), backlight is impossible.<br />
<br />
===Transreflective===<br />
It would be nice to have (the option of) a transreflective display, which while being less bright, is readable without needing to power the backlight. Then again, it depends on how much power the backlight uses compared to everything else...<br />
<br />
==="Slightly" Larger Screen===<br />
43mm x 57mm (2.8inch diagonal) is tiny. A 53mm x 71mm (3.5 inch diagonal) like on the TD035STEE1 would be a nice improvement. A widescreen format at about 53mm x 82.5mm instead of the 3:4 aspect ratio would be even cooler (if one could be found).<br />
<br />
===Second Display===<br />
A 32x32 OLED display possibly on the back for camera framing or on an edge so it can be viewed like a pager.<br />
This could be used to display any number of alerts (from any installed software) the alerts could have a dynamic prioritisation which means during the work day a message from the boss has high priority but lower at home (could be GPS/Time controlled?) multiple alerts shrink the icons to a 3x3 grid higher priority messages get more space.<br />
<br />
==Input devices==<br />
<br />
===No Dependence on Stylus===<br />
The Neo's basic functionality should be completely usable without a stylus, Like the iPhone but with stylus use for precision work.<br />
<br />
===A laser projection keyboard===<br />
Similar to [http://www.thinkgeek.com/computing/input/8193/ this], except the device would be integrated into the phone itself. Setting the Neo up on a stand on a flat surface (perhaps a stand could be built into the back of the Neo itself, or into a case) would turn the Neo into a micro-laptop. There may be several issues with the inclusion of this technology, including patents, the space required to project the laser grids, and the power consumption. If possible, however, it would make text input a breeze.<br />
<br />
===Just a few more Buttons===<br />
<br />
2 buttons more, 3 buttons total, mounted sideways would be enough. You could use them for play/pause and loudness controll while the phone remains in your pocket (display locked, ...), reading mails, rss, ebooks,... without wasting display space and so on.<br />
<br />
With 5 buttons in total you could possibly emulate a keyboard (2^5 = 32 combinations) for those who know how to play a flute. Useable onehanded, not wasting display space and faster than t9. (It's not faster than T9 - I've used this system with the microwriter agenda --[[User:Speedevil|Speedevil]] 00:00, 2 July 2007 (CEST)) Hopefully this is not patented already.<br />
<br />
===D-Pad and Buttons===<br />
*Adding a D-pad (to the bottom of the phone) and 2 to 4 buttons (to the top) would provide some tactile input controls, in addition to the touchscreen. They could be used as shortcut keys in the menu, or playback control when playing media. When the phone is held sideways, they can be used as games controls. (With touchscreen alone, gameplay options are limited)<br />
<br />
Game buttons would be best on both sides of the screen. The larger the buttons, the better. 2x 4 buttons in up-down-left-right configuration + some extra buttons separately a bit lower on the device would be good for many for emulation games. <br />
<br />
Here is a concept drawing of a possible neo1973 gaming version: <br />
(This has a 4-way direction pad, 8 way may be better for gaming)<br />
<br/><br />
[[Image:Neogame90.jpg]]<br />
<br/><br />
Shoulder buttons would be a great addition, too. It would be interesting if there was a total 4 of them, one for every corner. It would make the phone very flexible for rotating and 2 to 6 players playing on one device.<br />
<br/><br />
:''Note'' : The [http://en.wikipedia.org/wiki/Tapwave_Zodiac Tapwave Zodiac] Palm PDA / Game console hybrid had a similar setup - with an analog stick on the left (also used for quick selection using a radial main menu when working as a PDA), 4 buttons on the right (also configurable for shortcuts when using the device as PDA), and 2 shoulder buttons. Also it had and still has an enthusiastic scene of homebrew development (almost any console emulator for PalmOS can also take advantage of the additional buttons and graphic power of the device). If we also take into account the success encountered by the [http://en.wikipedia.org/wiki/GP32 GP32] in the past and the [http://en.wikipedia.org/wiki/GP2X GP2X] currently on the homebrew scene, it's not unreasonable to plan a future OpenMoko device with both a SmartPhone/PDA functionnality ''and'' hand-held console targeting homebrew development.<br />
<br />
===Thumb keyboard or keyboard attachment accessory===<br />
*Could be slide out or clamshell (hinge on long side) design with an external OLED. The keyboard should be protected when not in use.<br />
*Could be a clip on keyboard that attaches to the serial port or communicates by bluetooth (not preferred for permanent keyboard users).<br />
*Cheap clippable miniusb keyboard<br />
*One of the layouts proposed in [[Hardware:Keyboards]]<br />
* What about virtual keyboard? [[http://www.extremetech.com/article2/0,3973,539778,00.asp Keyboard]]<br />
<br />
===Analogue Controllers===<br />
<br />
====Trackball====<br />
A trackball would provide an efficient mouse-like interface in a very compact package. As exemplified in the newer Blackberry&reg; models.<br />
Maybe instead an optical sensor as are used in mice could be used so that the whole phone can be moved over a surface just like a mouse. (It could function as a Bluetooth mouse for other devices like laptop computers: see [[Bluetooth_Support#Acting_as_HID_device]]. Adding one other two-axis analogue input (possibly just the screen) would make the Neo usable as a TrackPoint or scroll-and-tilt mouse.) The same sensor might be usable as a barcode reader.<br />
<br />
====Analog Joystick====<br />
A joystick, or [http://www.extremetech.com/article2/0,1697,1772689,00.asp Rollermouse]-like device would provide additional control, compared with touchscreen only.<br />
*A standard [http://en.wikipedia.org/wiki/Pointing_stick pointing stick (ie. TrackPoint)] might serve well. As a fairly standard part, might they be quite inexpensive?<br />
<br />
====Dual analogues====<br />
Dual analogue controllers (one trackball or joystick above, one below the screen, most likely) might even be feasible. That might be overkill since the accelerometers or touchscreen can be used to provide a second analogue input. But it would be nice to have four axes of analogue control without having to tilt the screen away from you or partly cover it with your hand.<br />
<br />
===TV/radio receiver===<br />
[[Digital Television]], [[Digital Radio]] or even normal analogue TV/radio is widely available in the world, though unfortunately in various different forms. In markets where one standard is widespread, and hardware is suitable, it would be a great extension of the phone to a general entertainment device for when you're away from home. Multi standard devices would be ideal, but may not be small, low-power, or cheap.<br />
A good start would be an FM tuner, since it's one of the most widely used formats of radio broadcasting in the world.<br />
<br />
This could be a good chip, though it's not clear if the drivers are open source. http://www.sigmatel.com/products/portable/wireless/fmtuner.aspx#fragment-14<br />
<br />
===Accelerometer=== <br />
This enables the phone to sense which direction 'down' is, and to sense any movements the phone makes.<br />
<br />
See [[Accelerometer Fundamentals]] for more information on accelerometers as they may be used in phones.<br />
<br />
In some cases integrated gyroscopes may also be needed. A [[#Digital compass]] can even be of more use since it gives absolute rotation so slow rotations could also be measured. A 3D compass would be nicest, but a simple 2D compass already is a helpful addition to the accelerometers.<br />
<br />
*[[Wishlist:3D Viewport|3D Viewport]]<br />
*[[Wishlist:Computer Mouse|Computer Mouse]]<br />
*[[Wishlist:Determine Position|Determine Position]]<br />
*[[Wishlist:Dynamic Screen Orientation|Dynamic Screen Orientation]]<br />
*Change media player playlist when jogging vs walking. <br />
*Attempt to use to stabilise any future camera.<br />
<br />
This feature is scheduled for inclusion in the phase 2 Neo1973, currently slated for release in October 2007.<br />
<br />
===Side-Mounted Touch Strip===<br />
Add a "touch strip" sensor onto the side of the phone which can be used to scroll. By having it on the side you can use your thumb to scroll comfortably while holding the phone one-handed. An 8-element capacitive sensor would work wonderfully and be easy to fab using either a Quantum QT411 (http://www.qprox.com/products/qslide_qt411.php) or Analog Devices AD7143 (http://www.analog.com/en/prod/0,2877,AD7143,00.html) controller. The Analog Devices chip seems better suited due to it's smaller allowable element size.<br />
*With the AD7143 you can have an 8-element (128-position) 25mm long strip - Perfect!.<br />
*With a few OLED screens beneath the strip it could be used as dynamic configurable buttons/alerts eg. zoom/flash/shutter with a camera application and SMS/Email/Voicemail alerts in standby<br />
<br />
<br />
:Maybe it would be also possible to use is as finger print reader? --[[User:Tolein|tolein]] 20:18, 1 October 2007 (GMT+1)<br />
<br />
===Heart Rate Compatibility=== <br />
<br />
An RF interface to receive data from popular heart rate straps (Polar, Garmin, Sigma, Suunto, etc.). This would go along well with the existing GPS functionality and possible future Accelerometer functionality to make for a full-blown workout tool.<br />
<br />
Software can be written to track heart rate along a running, cycling, skiing, swimming loop, to monitor max and min heart rate, to match heart rate data to GPS coordinates and print map data w/ relevant data.<br />
<br />
===Digital compass=== <br />
A digital compass is useful for orienting maps to the terrain and other location/direction/orientation based applications (... is 300 meter that way) when the user is standing still (regardless of GPS reception) and for following a bearing when GPS reception is poor or speed is low. Also could be used to make the accelerometer data more exact.<br />
<br />
Very small [[I2C]] sensors like [http://www.ssec.honeywell.com/magnetic/hmc6352.html Honeywell's HMC6352 2-Axis Digital Integrated Compass] (6.5 x 6.5 x 1.5 mm) are very appropriate for this.<br />
<br />
*[[Wishlist:Auto Align Map]]<br />
<br />
See [[Wishlist - Hardware: Digital compass]] for more information<br />
<br />
===Thermometer===<br />
An electronic thermometer might become handy for some users.<br />
<br />
There are very small [[I2C]] devices available, that could easily integrate to the existing bus. For example [http://focus.ti.com/docs/prod/folders/print/tmp100.html this one from ti].<br />
(Could just be cheap and use the thermometer from the battery, thats how they did it in the nokia 5140's). Also is integrated in a barometer/altimeter like the SMD500 mentioned in [[Wish List - Hardware - Atmospheric]].<br />
<br />
===Barometer and Variometer (Altimeter)===<br />
<br />
A Barometer measures air pressure. This can be used to give weather information, and also as a variometer, to sense relative altitude. Variometers are commonly used in flying microlight and ultralight aircraft, to get accurate relative altitude.<br />
<br />
These are also common on high end GPS units. This is a great feature for walkers as you can tell how far you have got on any accent/decent.<br />
<br />
See [[Wish List - Hardware - Atmospheric]] for more information.<br />
<br />
===Finger print sensor===<br />
A fingerprint sensor gives easy and fast access to the phone, could lock the touchscreen etc. An example of this device can be found at [http://www.sonystyle.com/is-bin/INTERSHOP.enfinity/eCS/Store/en/-/USD/SY_BrowseCatalog-Start?CategoryName=cpu_VAIONotebookComputers_UX_Series&Dept=computers Sony UX17].<br />
<br />
Most fingerprint sensors in the embedded market include a navigation mode, where they work similar to either a touch-stick or touch-pad of a laptop.<br />
<br />
===Barcode Scanner===<br />
*less cpu intensive and more reliable than camera+ocr<br />
*though, bluetooth-enabled readers are already available.<br />
<br />
===Light Sensor===<br />
Ability to sense ambient light, and act accordingly. i.e if it's 3am and LightValue<.1 then Ring Quietly.<br />
<br />
===Wheel===<br />
A navigation wheel like on a sony/ericsson 810i would be nice.<br />
<br />
===Proximity Sensor===<br />
Switch off backlight when you place the phone to your ear. Prevent accidental activation of speakerphone or other sounds when the phone is near the ear (prevent hearing damage). Possibly switch the speakerphone on or off automatically depending on if the phone is by your head or not.<br />
<br />
=== Make ''all'' unlocking of phone, password protected===<br />
<br />
When my (current non-neophone) phone is in my pocket and I have it locked, it sometimes accidentally unlocks itself since only two keystrokes in the correct order are necessary to unlock it. When it's unlocked and still in my pocket it sometimes calls someone without my knowledge. All phones I've seen today have a press-just-one-button bypass to answer an incoming call even when the phone is locked. I suggest making the locking mechanism let the user configure it so that the user has to enter a password even for answering incoming calls. The likeliness of the phone accidentally runbbing against my car keys, hitting a ten character long password, unlocking the phone without my knowledge and consent is low enough even for us most unlucky users.<br />
<br />
==Expansion==<br />
===Positioning of Buttons, Connections and ports===<br />
<br />
Ideally any cable ports such as charging, USB, audio, docking should not get in the way of your hand or fingers when holding it in it's normal orientation. For the sake of SDIO cards an external SD slot should be on the top edge. IR for remote control software and ease of inter-device communication should be on the corner so that it is facing away from you for both orientations. Buttons obviously are positioned for finger control. An example of how '''not''' to do this would be the HTC Universal<br />
<br />
===Storage===<br />
<br />
====MMC/SD/SDIO slot (rather than?) miniSD or microSD====<br />
*Cheaper, more durable cards in a widely accepted format.<br />
*Much much larger storage capacity, [http://blog.scifi.com/tech/archives/2007/08/23/toshiba_unleash_1.html even 32GB]<br />
*Cards are harder to lose<br />
*Wider selection of accessories, including SDIO accessories.<br />
*Make externally available so that larger length SDIO cards can be used (thinking about SDIO WLAN here)<br />
*[http://en.wikipedia.org/wiki/Secure_Digital_card#SDHC SDHC] compatible. It seems to already have the right hardware for it - see [[Neo1973_Hardware#microSD-Card]].<br />
<br />
====Two SD slots====<br />
*Micro SDHC for /home partition. Keep like current design underneath SIM card<br />
*Hot swappable externally accessible normal size SDHC/SDIO slot<br />
<br />
===Local Communication===<br />
<br />
====USB====<br />
* 5V Powered, to avoid having to carry around a hub for when you want to occasionally plug in a memory stick. Many powered hubs will not recognize a totally unpowered host. Provide a maximum current to drive a basic USB keyboard/memory stick/mouse/webcam/astrowebcam. This could be done by adding a small cheap power converter like the [http://www.national.com/pf/LM/LM2753.html LM2753]<br />
* USB 2.0 <br />
* Standard type A socket for quick & easy insertion of memory sticks etc.<br />
* OTG (is this maybe supported already ?)<br />
* Bootable USB device emulation: the possibility to boot any computer on a bootable flagged partition of the transflash.<br />
* Protection against incorrectly wired USB ports: some USB ports are wired incorrectly; if the +5V and GND are swapped, the device would get -5V when it's expecting +5V, which could burn some chips. A reverse-biased diode between +5V and GND, D+ and GND, D- and GND, and (if used) ID and GND, with a low enough forward voltage drop (to limite the negative voltages to what the chips can withstand), would protect the device by tripping the port's short circuit protection.<br />
<br />
====Wireless USB support====<br />
[http://en.wikipedia.org/wiki/Wireless_USB Wireless USB] is the wireless version of USB offering data-rates up to 480 Mbit/s over short distances (<3 meter). Chipsets suitable for a phone are likely to take some time to be available.<br />
<br />
====SIR/FIR transceiver (Serial Infrared) / IR remote control====<br />
*An infrared transceiver is cheap, small, and useful for sync with many laptops and mobile phones. <br />
*Replace/emulate all IR-based remote controls used for your tv, vcr, etc on your neo cell phone.<br />
** replaces multiple 'dumb' devices with a single intelligent device (your neo) that you will probably carry with you at all times anyway. <br />
**Command sets should be retrieved from a database or learned from other less intelligent remote control devices with macros. <br />
**reduces clutter, particularly in the living room.<br />
**inceases the neo's practical status as an 'always-have' device. <br />
<br />
Other uses.<br />
*Detecting reflections from inside of a caddy, and switching from active mode.<br />
*FIR would be a nice option, as it's some 40 times faster than SIR.<br />
<br />
===Other===<br />
<br />
====Video Out====<br />
*Through a docking port<br />
**S-Video/Composite Out<br />
**DVI Out<br />
<br />
==Output devices==<br />
<br />
===LED===<br />
*The Neo1973 GTA02 will have LEDs of some sort behind at least one button. [http://lists.openmoko.org/pipermail/community/2007-July/008458.html]<br />
*A blinking LED would be a cheap, low power way to inform the user of new SMS/Email....<br />
**An alternative to this would be for one small part of the LCD to be separately backlit.<br />
**This requires the CPU and LCD to be somewhat active, to keep the LCD refreshed, but gives much more information.<br />
**A Small OLED Screen could be used and display much more information than a LED with minimal power usage.<br />
<br />
*For example a multicolor LED which pulses yellow for GSM/GPRS transmit, blue for Bluetooth/Wifi, green to indicate non-urgent information - missed call etc, red to indicate battery low or other urgent notices.<br />
<br />
**The LED and button ideas could be combined: illuminated buttons.<br />
**It must be possible to completely disable the LED to save power or other personal preferences.<br />
<br />
=== Flashlight ===<br />
For finding keys, or any other application. May also optionally pulse in time with ring, to make phone more visible.<br />
This is really well done in Nokia 5500.<br />
<br />
=== FM transmitter ===<br />
Small FM transmitter to output to car, and other nearby radios.<br />
<br />
===HAC Compliance===<br />
[http://quux.wiki.zoho.com/WhereAreHACphones.html Here] is some summary/discussion of how hearing aid compliance rules work in the US. Specifically it would be nice to see the phone include a [http://www.hearingresearch.org/Dr.Ross/telecoil_and_telephones.htm telecoil], which allows the phone to connect wirelessly to many standard hearing aids.<br />
<br />
==Mobile Communication options==<br />
<br />
===Generic Access Network / Unlicensed Mobile Access===<br />
This technology requires cooperation from the cellular provider, but [http://en.wikipedia.org/wiki/Unlicensed_Mobile_Access UMA/GAN] is already offered by T-Mobile in the United States, and perhaps others in other countries. Allowing the user to roam from GSM to wifi, this technology can save the end user a significant amount of money, and also allow the user to deploy coverage where there was none before. There are only a few UMA capable phones currently, but it would be great if this could be made to work on a phase 2 type OpenMoko device.<br />
<br />
Note that this features requires a more advanced access to the GSM modem. Special messages needs to be exchanged with the network.<br />
<br />
===Faster/better mobile connectivity.===<br />
[http://en.wikipedia.org/wiki/Gsm GSM]/[http://en.wikipedia.org/wiki/GPRS GPRS] is at best slow. An incremental improvement would be a radio with [http://en.wikipedia.org/wiki/EDGE EDGE ] support. EDGE is an evolved GSM standard and, like GPRS, it operates on the same frequency as voice. This means a quad-band EDGE radio will have near-complete worldwide coverage. <br />
<br />
[http://en.wikipedia.org/wiki/UMTS UMTS] - which is widespread in Europe and being deployed in the US, [http://en.wikipedia.org/wiki/HSDPA HSDPA] (asia) and any other mobile standards would be nice for faster data connectivity and coverage.<br />
It is unlikely that all of these will be supported initially, but it is a goal. These faster standards operate in different frequencies from GSM/GPRS/EDGE. Which frequency exactly will depend on the carrier and country. For UMTS in the US, AT&T uses 850/1900 MHz but T-Mobile will use 2100/1700 MHz for example.<br />
<br />
Until that goal is reached, it is likely that some phones will be brought out for various specific markets - Europe, Asia, US.<br />
<br />
===Ability to use multiple SIMs/networks===<br />
* External SIM sockets are widely available in China, a dual external socket would be a very good solution.<br />
* [http://www.fonefunshop.co.uk/dualsim/digital.htm Dual SIM card kit] - two SIMs are trimmed and combined, software supportwould be needed, and both can't be used at once...<br />
* Some networks support multiple numbers on one SIM. Unfortunately this won't allow split networks.<br />
* A second/dual GSM module would allow full use of both sims at all times.<br />
* As a hack, [http://wiki.openmoko.org/wiki/Wish_List#Bluetooth_powered_Multi-SIM_support use another mobile via BT].<br />
** As many as three SIM slots would be genuinely useful, especially for a 3G phone - some 3G data tariffs are only available on data-only SIMs. A user could quite reasonably have one SIM for data, once SIM for his personal voice calls, and a third SIM for his business number.<br />
<br />
===PMR446/FRS Radio===<br />
* Include a PMR/FRS Radio.<br />
* A two-way walkie talkie lets you use the phone to communicate with friends without requiring a GSM connection (crowded networks at festivals, at locations with no GSM coverage).<br />
<br />
===[[DECT]]===<br />
* Include a [[DECT]] GAP/CAT-iq transceiver so you can use your home and/or office PSTN line<br />
** Ability to use Alcatel phonebook stuff (like provided by the eventphone.de phone equipment) would be very nice too<br />
<br />
===[[SIP phone]]===<br />
Make stripped down (and thus cheaper) version of the Neo1973 phone for use as a SIP phone. Remove GPS, GSM, accelerometers, stilus.<br />
<br />
Addition of an centimeters-precise location system [http://en.wikipedia.org/wiki/Real_Time_Location_Systems RTLS] would be nice, as it will allow highly sensible indoor context detection. Image to put the phone next to your mirror (where you shave daily) and observe it automatically switch to news radio channel. Or put it next to your bed and see it automatically switch to "sleeping" mode, when only calls from predefined numbers are accepted.<br />
<br />
==Casing==<br />
See also: [[Alternate Neo1973 case designs]] for a list of cases being considered for design/manufacture by the community.<br />
<br />
===[[Expansion Back]]===<br />
* Replacement backs with additional features ranging from solar power, larger batteries, extra hardware, ...<br />
<br />
===Space efficient Lanyard===<br />
The hole at the bottom of the phone takes a lot of space. A [http://en.wikipedia.org/wiki/Kensington_Security_Slot Kensington Security Slot] could be used instead.<br />
<br />
=== Ruggedized version ===<br />
We need something you can drop from 4 feet in to a puddle of dirty water on construction site. Sunlight readable display. The big ugly pseudo military version.<br />
<br />
=== Transparent ===<br />
Make a transparent, see-through casing. Why do we need a closed casing for open hardware and open software? Show the world it is a truly Free/Open source phone.<br />
<br />
===[[Wishlist:Expansion Front|Expansion Front]]===<br />
Replacement fronts with e.g. extra buttons.<br />
<br />
<br />
<br />
==Misc==<br />
===Galileo/GLONASS/GPS receiver===<br />
*A multi-standard satellite positioning module would be nice eventually, it does not seem to be near-term due to chipset availability problems. Galileo is the to be launched (2011) European positioning system. GLONASS is the already existing Russian one.<br />
<br />
===X10 RF Remote===<br />
Many PC-based media centers are being equipped with an RF (433 MHz) / X10-based remote control. The [http://en.wikipedia.org/wiki/X10_(industry_standard) X10] protocol also facilitates home automation to control lamps, switches, etc.<br />
The advantages of using RF for control instead of Infra-red this that it also works when furniture, walls, or doors are blocking the path between RF remote and the equipment or device. [http://www.lirc.org/ Lirc] supports X10-based RF remotes (but expects having an USB RF receiver attached to the media center).<br />
<br />
===RFID tag/RFID Reader===<br />
* Implementation/Cooperation with: [http://www.rfidguardian.org/ RFID-Guardian]<br />
*An enable-able tag would be of use - for example being able to use the phone to open doors, or cars. Unfortunately, it's moderately hard to do secure programmable tags that are compatible with existing systems, for obvious reasons.<br />
* Say you have RFID tags on your personal belongings: cellphone, keys... Neo could be programmed to remember the last recorded GPS location before it lost contact with the respective RFIDs. It'd be trivial to check where you left your cellphone, get directions from a map...or beep when the phone gets out of RFID range.<br />
<br />
===Less weight===<br />
* Work on the weight of the Neo1973 and following devices. At the present time the Neo1973 is just a moderate / normal business or multimedia phone. The ordinary "user" may want something lighter. Take a look at the following table, that's the Neo1973 compared with other common bussiness or multimedia phones.<br />
{|border="1"<br />
| Neo1973 || Fujitsu-Siemens LOOX N560 || E-Ten Glofiish X500+ || Sony Ericsson P990i || iPhone || Nokia E65 <br />
|- <br />
| 184 g || 160 g || 146 g || 150 g || 135 g || 115 g <br />
|-<br />
|}<br />
<br />
===Make it smaller===<br />
* To stay within physical matters: Maybe the Neo1973 is also just a normal business/multimedia phone when looking at the size. It would be great the shrink it a bit. Especially the thickness of 18.5 mm could be worked on!<br />
<br />
===Standard 3.5mm headphone jack===<br />
The Neo1973 uses a 4-conductor 2.5mm jack for stereo headphones and a microphone. A 2.5mm jack is the most common for headsets. <br />
<br />
There is an emerging convention used in the Nokia N800 and some other devices. A 4-conductor 3.5mm jack that can use a microphone with special headsets, but can also be used with off-the-shelf 3.5mm stereo headphones. Adapters to 2.5mm are of course available and this 3.5mm jack is much more robust.<br />
<br />
Neglecting space limitations, multiple sockets - 2.5mm and 3.5mm would be nice. Probably not practical in a phone. Other expanded plugs might allow remote controls.<br />
<br />
Other uses might be better met using bluetooth, or USB audio.<br />
<br />
===Laser Pointer===<br />
Include a built in laser pointer. Everything is better with lasers.<br />
<br />
===Completely free hardware===<br />
Consider selling one device with absolutely no non-free components in it, even if that means dropping the GSM support. I believe having one such device available would be good, because then it could be recommended by organizations like the FSF which typically never recommends anything if it has even a little non-free code in it.<br />
<br />
=== Consider economy / inexpensive / less featured edition ===<br />
Some people want less features, because they do not need them. Leaving out some features either lets the phone get smaller or possibly enhances battery live.<br />
<br />
One big suggestion in this area is a b/w lower res display instead of the big color display.<br />
<br />
=== Inductive Charger ===<br />
<br />
It would be nice if it was possible to charge the phone without having to connect a cable. I'd like to have a simple docking station with an inductive charger like the type that's used for electric toothbrushes [http://home.howstuffworks.com/question292.htm ]. The charger itself could get its power from a standard wall-wart power supply, or it could be USB/Firewire powered.<br />
<br />
==Related Hardware==<br />
See [[Related Hardware]]<br />
<br />
[[Category:Hardware ideas| ]]<br />
[[Category:User]]</div>Bashttp://openmoko.org/wiki/Wish_List_-_HardwareWish List - Hardware2007-10-11T09:11:30Z<p>Bas: /* TV/radio receiver */</p>
<hr />
<div>This page details hardware features which some would like to go into future phones similar to the [[Neo1973]].<br />
<br />
Related pages are:<br />
*[[Wishlist - Hardware - Novel Devices]] - openmoko will run on a large number of devices in the future, some of which may be DVD players, cameras, or convergance devices. <br />
*[[Wishlist:Unlikely]] - Hardware that is unlikely to appear in any OpenMoko device, due to it being impossible to fabricate with near-term technology, or for other reasons.<br />
*[[Wishlist:Accessories]] - Accessories that people would like, that connect easily to the phone - initially primarily for the Neo1973 <br />
*[[Wishlist:Expansion]] - add-ons to the phone, maybe involving hardware changes, and software and hardware protocols to implement these.<br />
<br />
This page is rather long. Before adding a new idea, please read through this page and the above pages, to make sure your idea has not been suggested before.<br />
<br />
==Processor==<br />
===AT91CAP9S500A (ARM9 + FPGA-port)===<br />
Why FPGA?:<br />
*[http://hardware.silicon.com/servers/0,39024647,39166443,00.htm?r=1 20 March 2007 Green supercomputer is 'go' in Scotland] Quote: "...A supercomputer 10 times more energy efficient and up to 300 times faster than its traditional equivalents..."<br />
<br />
Take a look at this microcontroller, that integrates an ARM9 microcontroller and a dedicated FPGA port: AT91CAP9S500A. It has "only" a max. clock at 200MHz, but can use a FPGA for hardware acceleration, that could be used for video (de)compression, [http://en.wikipedia.org/wiki/AacPlus_v2 aacPlus v2]/[http://en.wikipedia.org/wiki/HE-AAC_v2 HE-AAC v2] sound (de)compression and many other things. HE-AAC v2 is better than [http://en.wikipedia.org/wiki/MP3 MP3].<br />
*[http://www.atmel.com/dyn/products/product_card.asp?family_id=689&family_name=AT91CAP+Microcontrollers&part_id=4137 AT91CAP9S500A] Quote: "...The AT91CAP9S500A is built around a 12-layer bus matrix, allowing a maximum internal bandwidth of twelve 32-bit buses. Its distributed DMA architecture enables multiple data transfers to take place between the processor, memories and peripherals with minimal processor overhead...".<br />
*[http://www.atmel.com/dyn/resources/prod_documents/doc6310.pdf GNU-Based Software Development on AT91SAM Microcontrollers]<br />
*Maybe this is a good tool?: [http://www.jhdl.org/ BYU JHDL, Open Source FPGA CAD Tools]<br />
*[http://www.eetimes.com/showArticle.jhtml;?articleID=197002705 02/05/2007, FPGA tool bottleneck stalls HPC] Quote: "...Current FPGA synthesis, placement and routing tools are written for hardware designers, not software programmers simply trying to accelerate an algorithm..."<br />
<br />
This seems to be a good hardware mix (ARM+FPGA). It does [http://en.wikipedia.org/wiki/Theora Ogg Theora] or [http://en.wikipedia.org/wiki/MJPEG MJPEG] in the FPGA with 1 million gates:<br />
*http://sourceforge.net/projects/elphel, [http://wiki.elphel.com/index.php?title=10353 board 10353], [http://wiki.elphel.com/index.php?title=Camera_hardware camera hardware], [http://wiki.elphel.com/index.php?title=Main_Page Main page], [http://www.elphel.com/articles/index.html Imaging solutions with Free software and open hardware]<br />
<br />
Just another FPGA+microcontroller example: <br />
*[http://melzer.ch/html/body_alya.html The Alya Project] ([http://home.nikocity.de/andymon/hfg/Alya/alya.html old page])<br />
*[http://melzer.ch/ALYA.ASM PIC assembler source code], [http://melzer.ch/ALYA.TDF Altera FPGA code]. Schematic: [http://melzer.ch/Schaltplan1.gif], [http://melzer.ch/Schaltplan2.gif], [http://melzer.ch/Schaltplan3.gif]<br />
<br />
I do not think this means what you think it means... I read "...and a metal programmable (MP) block of 500K gates of digital logic." as meaning that it's a one-time programmable block, more akin to a standard-cell ASIC than an FPGA. This is supported by the fact that their development board contains a separate FPGA chip. Now, granted, having a 500K gate ASIC on board an ARM is a cool thing... but not quite as cool as this chip appeared at first glance.<br />
<br />
===Samsung S3C2443===<br />
*[http://www.samsung.com/global/business/semiconductor/productInfo.do?fmly_id=229&partnum=S3C2443&&ppmi=1427 Samsung S3C2443] Up to 533 MHz, USB 2.0<br />
<br />
==Possible FPGA==<br />
This FPGA is just an example:<br />
*[http://www.xilinx.com/products/silicon_solutions/fpgas/spartan_series/spartan3an_fpgas/capabilities/index.htm Spartan-3AN FPGA Capabilities] Quote: "...Simple and secure embedded application storage with up to 11Mb of integrated user Flash...Enable simple arithmetic and math functions as well as advanced DSP functions to derive over 330 Giga MACs/sec...Up to 32 18 x 18 embedded multipliers support 18-bit signed or 17-bit unsigned multiplication, and can be cascaded to support wider bits..."<br />
**XC3S1400AN-4FGG676CES $91<br />
**XC3S200AN-4FTG256CES $25.87<br />
<br />
====Tool for FPGAs====<br />
*[http://www.xilinx.com/ise/logic_design_prod/webpack.htm xilinx.com: ISE WebPACK is the industry´s only FREE, fully featured front-to-back FPGA design solution for Linux, Windows XP, and Windows Vista]<br />
<br />
===Asynchronous FPGA, AFPGA===<br />
*[http://www.achronix.com/products.html Achronix-ULTRA]<br />
**[http://www.pldesignline.com/news/186700955 Achronix preps 2-GHz Asynchronous FPGA for sampling in 2007]<br />
**[http://vlsi.cornell.edu/fpga.php Asynchronous VLSI and Architecture, Cornell University: Asynchronous Field-Programmable Gate Arrays (AFPGAs)] Quote: "...integrated pipelining support..."<br />
**[http://citeseer.ist.psu.edu/teifel03programmable.html Programmable Asynchronous Pipeline Arrays (2003) John Teifel, Rajit Manohar]<br />
<br />
==Internal Memory==<br />
===RAM===<br />
128MB Dedicated for open files, running software etc., not for storage, or 256MB at all would be really nice and enough for any future software.<br />
<br />
===ROM===<br />
Enough to Hold O/S and a fair number of applications and their settings. Persistent Storage with XIP capability. About 128 MB.<br />
<br />
===Storage===<br />
An internal Micro SDHC should be used for users' files and additional software<br />
<br />
==Wireless data networking==<br />
<br />
===WiMAX support===<br />
[http://en.wikipedia.org/wiki/Wimax WiMAX] is a high-speed data service, similar to wifi, though longer range and newer. Where service is available, this would complement WiFi. Unfortunately, unlike wifi, frequencies vary worldwide, so global usage may be complex.<br />
<br />
===Emerging Protocols===<br />
*[http://en.wikipedia.org/wiki/Near_Field_Communication Near Field Communication] has a few centimeter range, useable for keys, ID badges, pairing bluetooth devices and similar uses. Mentioned in newer bluetooth and SD standards. (No products.)<br />
*[http://en.wikipedia.org/wiki/ZigBee ZigBee] is designed for connecting sensors and switches in buildings, with many options including mesh networks and aggressive power saving compared to bluetooth. (Almost no products available.)<br />
*The [http://en.wikipedia.org/wiki/ANT_%28network%29 ANT network] is for connecting worn devices. Similar to ZigBee, but much simpler and maybe lower power. ([http://www.thisisant.com/?section=9 Short list] of products.)<br />
<br />
==Camera==<br />
<br />
* A camera that can take reasonable quality video and pictures is something many want. Applications vary from simple snapping, to gesture interfaces, video conferencing, barcode reading, buisness card reading, healthcare, servicing, and more.<br />
<br />
* Some people can't take cameras into work - a model without the camera, or some way of removing the camera would be useful or leave the camera chip in place and have a removable lens assembly and replacement backcover.<br />
<br />
* See [[Wishlist:Camera]] for a more detailed wishlist.<br />
<br />
==Display==<br />
===Multitouch screen===<br />
<br />
''Main article: [[Wishlist:Spell_weaving|Spell weaving]]''<br />
<br />
See also [http://pogue.blogs.nytimes.com/2007/03/27/the-multi-touch-screen/ this page] containing a link to a video demonstration.<br />
<br />
A history of multitouch implementations is [http://billbuxton.com/multitouchOverview.html here] ([http://google.com/search?q=cache:billbuxton.com/multitouchOverview.html google cache version])<br />
<br />
*Use examples: [http://www.youtube.com/watch?v=UcKqyn-gUbY&mode=related&search= Multi-touch interface (from Adobe TED)], [http://www.youtube.com/watch?v=1ftJhDBZqss&mode=related&search= Multi Touch (new touchscreen technology)]<br />
<br />
===Bigger and better screen===<br />
2.8" widescreen (like in [http://etencorp.com E-ten] PDA/smartphones), or 3.5" widescreen (like in [http://www.expansys.ie/d.aspx?i=134944 Fujitsu Siemens LOOX N560]).<br />
<br />
262k or 16.7M colurs for displaying images and especially videos.<br />
<br />
OLED for better contrast, more rich colours, and less energy consumption.<br />
<br />
Maybe the [http://www.sharpsme.com/Page.aspx/europe/en/part/LS037V7DW01/ LS037V7DW01] by Sharp could be a solution. It has nearly the same specs as the currently used, but 3,7" -- [[User:Wedge | Wedge]]<br />
<br />
===Distance sensing touchscreen===<br />
{{Main|Hardware:NearlyTouchScreen}}<br />
TouchKo's (now Wacom Company Ltd.) spatial capacitive "touchscreen", can sense fingers at a small distance, so you do not get your display greasy, and can unlike some touchscreens, be operated with gloves.<br />
<br />
===<s>Video acceleration</s>===<br />
Hardware acceleration for video playback and 2D/3D accelleration will be present in [[Neo1973 GTA02]].<br />
<br />
===EPD===<br />
Or electronic paper display, EPD is used in many new devices such as the new Motorola motofone, sonys new e-reader and Irex's iliad. The technology provides thin, lightweight, power saving screens using new eink technology. This technology could cut the weight of the phone and its power usage. For more info see: [http://www.eink.com eink's website].<br />
<br />
Pro: laserprinter like quality, glossy, very stable image, easy on the eyes. Electronics are similar to TFT. Very low power consumption. <br />
<br />
Con: Black and grey only (like a newspaper, but glossy), although there were already color prototypes in 2005. low framerate (5fps). Can reflect light (like paper), backlight is impossible.<br />
<br />
===Transreflective===<br />
It would be nice to have (the option of) a transreflective display, which while being less bright, is readable without needing to power the backlight. Then again, it depends on how much power the backlight uses compared to everything else...<br />
<br />
==="Slightly" Larger Screen===<br />
43mm x 57mm (2.8inch diagonal) is tiny. A 53mm x 71mm (3.5 inch diagonal) like on the TD035STEE1 would be a nice improvement. A widescreen format at about 53mm x 82.5mm instead of the 3:4 aspect ratio would be even cooler (if one could be found).<br />
<br />
===Second Display===<br />
A 32x32 OLED display possibly on the back for camera framing or on an edge so it can be viewed like a pager.<br />
This could be used to display any number of alerts (from any installed software) the alerts could have a dynamic prioritisation which means during the work day a message from the boss has high priority but lower at home (could be GPS/Time controlled?) multiple alerts shrink the icons to a 3x3 grid higher priority messages get more space.<br />
<br />
==Input devices==<br />
<br />
===No Dependence on Stylus===<br />
The Neo's basic functionality should be completely usable without a stylus, Like the iPhone but with stylus use for precision work.<br />
<br />
===A laser projection keyboard===<br />
Similar to [http://www.thinkgeek.com/computing/input/8193/ this], except the device would be integrated into the phone itself. Setting the Neo up on a stand on a flat surface (perhaps a stand could be built into the back of the Neo itself, or into a case) would turn the Neo into a micro-laptop. There may be several issues with the inclusion of this technology, including patents, the space required to project the laser grids, and the power consumption. If possible, however, it would make text input a breeze.<br />
<br />
===Just a few more Buttons===<br />
<br />
2 buttons more, 3 buttons total, mounted sideways would be enough. You could use them for play/pause and loudness controll while the phone remains in your pocket (display locked, ...), reading mails, rss, ebooks,... without wasting display space and so on.<br />
<br />
With 5 buttons in total you could possibly emulate a keyboard (2^5 = 32 combinations) for those who know how to play a flute. Useable onehanded, not wasting display space and faster than t9. (It's not faster than T9 - I've used this system with the microwriter agenda --[[User:Speedevil|Speedevil]] 00:00, 2 July 2007 (CEST)) Hopefully this is not patented already.<br />
<br />
===D-Pad and Buttons===<br />
*Adding a D-pad (to the bottom of the phone) and 2 to 4 buttons (to the top) would provide some tactile input controls, in addition to the touchscreen. They could be used as shortcut keys in the menu, or playback control when playing media. When the phone is held sideways, they can be used as games controls. (With touchscreen alone, gameplay options are limited)<br />
<br />
Game buttons would be best on both sides of the screen. The larger the buttons, the better. 2x 4 buttons in up-down-left-right configuration + some extra buttons separately a bit lower on the device would be good for many for emulation games. <br />
<br />
Here is a concept drawing of a possible neo1973 gaming version: <br />
(This has a 4-way direction pad, 8 way may be better for gaming)<br />
<br/><br />
[[Image:Neogame90.jpg]]<br />
<br/><br />
Shoulder buttons would be a great addition, too. It would be interesting if there was a total 4 of them, one for every corner. It would make the phone very flexible for rotating and 2 to 6 players playing on one device.<br />
<br/><br />
:''Note'' : The [http://en.wikipedia.org/wiki/Tapwave_Zodiac Tapwave Zodiac] Palm PDA / Game console hybrid had a similar setup - with an analog stick on the left (also used for quick selection using a radial main menu when working as a PDA), 4 buttons on the right (also configurable for shortcuts when using the device as PDA), and 2 shoulder buttons. Also it had and still has an enthusiastic scene of homebrew development (almost any console emulator for PalmOS can also take advantage of the additional buttons and graphic power of the device). If we also take into account the success encountered by the [http://en.wikipedia.org/wiki/GP32 GP32] in the past and the [http://en.wikipedia.org/wiki/GP2X GP2X] currently on the homebrew scene, it's not unreasonable to plan a future OpenMoko device with both a SmartPhone/PDA functionnality ''and'' hand-held console targeting homebrew development.<br />
<br />
===Thumb keyboard or keyboard attachment accessory===<br />
*Could be slide out or clamshell (hinge on long side) design with an external OLED. The keyboard should be protected when not in use.<br />
*Could be a clip on keyboard that attaches to the serial port or communicates by bluetooth (not preferred for permanent keyboard users).<br />
*Cheap clippable miniusb keyboard<br />
*One of the layouts proposed in [[Hardware:Keyboards]]<br />
* What about virtual keyboard? [[http://www.extremetech.com/article2/0,3973,539778,00.asp Keyboard]]<br />
<br />
===Analogue Controllers===<br />
<br />
====Trackball====<br />
A trackball would provide an efficient mouse-like interface in a very compact package. As exemplified in the newer Blackberry&reg; models.<br />
Maybe instead an optical sensor as are used in mice could be used so that the whole phone can be moved over a surface just like a mouse. (It could function as a Bluetooth mouse for other devices like laptop computers: see [[Bluetooth_Support#Acting_as_HID_device]]. Adding one other two-axis analogue input (possibly just the screen) would make the Neo usable as a TrackPoint or scroll-and-tilt mouse.) The same sensor might be usable as a barcode reader.<br />
<br />
====Analog Joystick====<br />
A joystick, or [http://www.extremetech.com/article2/0,1697,1772689,00.asp Rollermouse]-like device would provide additional control, compared with touchscreen only.<br />
*A standard [http://en.wikipedia.org/wiki/Pointing_stick pointing stick (ie. TrackPoint)] might serve well. As a fairly standard part, might they be quite inexpensive?<br />
<br />
====Dual analogues====<br />
Dual analogue controllers (one trackball or joystick above, one below the screen, most likely) might even be feasible. That might be overkill since the accelerometers or touchscreen can be used to provide a second analogue input. But it would be nice to have four axes of analogue control without having to tilt the screen away from you or partly cover it with your hand.<br />
<br />
===TV/radio receiver===<br />
[[Digital Television]], [[Digital Radio]] or even normal analogue TV/radio is widely available in the world, though unfortunately in various different forms. In markets where one standard is widespread, and hardware is suitable, it would be a great extension of the phone to a general entertainment device for when you're away from home. Multi standard devices would be ideal, but may not be small, low-power, or cheap.<br />
A good start would be an FM tuner, since it's one of the most widely used formats of radio broadcasting in the world.<br />
This could be a good chip, though it's not clear if the drivers are open source. http://www.sigmatel.com/products/portable/wireless/fmtuner.aspx#fragment-14<br />
<br />
===Accelerometer=== <br />
This enables the phone to sense which direction 'down' is, and to sense any movements the phone makes.<br />
<br />
See [[Accelerometer Fundamentals]] for more information on accelerometers as they may be used in phones.<br />
<br />
In some cases integrated gyroscopes may also be needed. A [[#Digital compass]] can even be of more use since it gives absolute rotation so slow rotations could also be measured. A 3D compass would be nicest, but a simple 2D compass already is a helpful addition to the accelerometers.<br />
<br />
*[[Wishlist:3D Viewport|3D Viewport]]<br />
*[[Wishlist:Computer Mouse|Computer Mouse]]<br />
*[[Wishlist:Determine Position|Determine Position]]<br />
*[[Wishlist:Dynamic Screen Orientation|Dynamic Screen Orientation]]<br />
*Change media player playlist when jogging vs walking. <br />
*Attempt to use to stabilise any future camera.<br />
<br />
This feature is scheduled for inclusion in the phase 2 Neo1973, currently slated for release in October 2007.<br />
<br />
===Side-Mounted Touch Strip===<br />
Add a "touch strip" sensor onto the side of the phone which can be used to scroll. By having it on the side you can use your thumb to scroll comfortably while holding the phone one-handed. An 8-element capacitive sensor would work wonderfully and be easy to fab using either a Quantum QT411 (http://www.qprox.com/products/qslide_qt411.php) or Analog Devices AD7143 (http://www.analog.com/en/prod/0,2877,AD7143,00.html) controller. The Analog Devices chip seems better suited due to it's smaller allowable element size.<br />
*With the AD7143 you can have an 8-element (128-position) 25mm long strip - Perfect!.<br />
*With a few OLED screens beneath the strip it could be used as dynamic configurable buttons/alerts eg. zoom/flash/shutter with a camera application and SMS/Email/Voicemail alerts in standby<br />
<br />
<br />
:Maybe it would be also possible to use is as finger print reader? --[[User:Tolein|tolein]] 20:18, 1 October 2007 (GMT+1)<br />
<br />
===Heart Rate Compatibility=== <br />
<br />
An RF interface to receive data from popular heart rate straps (Polar, Garmin, Sigma, Suunto, etc.). This would go along well with the existing GPS functionality and possible future Accelerometer functionality to make for a full-blown workout tool.<br />
<br />
Software can be written to track heart rate along a running, cycling, skiing, swimming loop, to monitor max and min heart rate, to match heart rate data to GPS coordinates and print map data w/ relevant data.<br />
<br />
===Digital compass=== <br />
A digital compass is useful for orienting maps to the terrain and other location/direction/orientation based applications (... is 300 meter that way) when the user is standing still (regardless of GPS reception) and for following a bearing when GPS reception is poor or speed is low. Also could be used to make the accelerometer data more exact.<br />
<br />
Very small [[I2C]] sensors like [http://www.ssec.honeywell.com/magnetic/hmc6352.html Honeywell's HMC6352 2-Axis Digital Integrated Compass] (6.5 x 6.5 x 1.5 mm) are very appropriate for this.<br />
<br />
*[[Wishlist:Auto Align Map]]<br />
<br />
See [[Wishlist - Hardware: Digital compass]] for more information<br />
<br />
===Thermometer===<br />
An electronic thermometer might become handy for some users.<br />
<br />
There are very small [[I2C]] devices available, that could easily integrate to the existing bus. For example [http://focus.ti.com/docs/prod/folders/print/tmp100.html this one from ti].<br />
(Could just be cheap and use the thermometer from the battery, thats how they did it in the nokia 5140's). Also is integrated in a barometer/altimeter like the SMD500 mentioned in [[Wish List - Hardware - Atmospheric]].<br />
<br />
===Barometer and Variometer (Altimeter)===<br />
<br />
A Barometer measures air pressure. This can be used to give weather information, and also as a variometer, to sense relative altitude. Variometers are commonly used in flying microlight and ultralight aircraft, to get accurate relative altitude.<br />
<br />
These are also common on high end GPS units. This is a great feature for walkers as you can tell how far you have got on any accent/decent.<br />
<br />
See [[Wish List - Hardware - Atmospheric]] for more information.<br />
<br />
===Finger print sensor===<br />
A fingerprint sensor gives easy and fast access to the phone, could lock the touchscreen etc. An example of this device can be found at [http://www.sonystyle.com/is-bin/INTERSHOP.enfinity/eCS/Store/en/-/USD/SY_BrowseCatalog-Start?CategoryName=cpu_VAIONotebookComputers_UX_Series&Dept=computers Sony UX17].<br />
<br />
Most fingerprint sensors in the embedded market include a navigation mode, where they work similar to either a touch-stick or touch-pad of a laptop.<br />
<br />
===Barcode Scanner===<br />
*less cpu intensive and more reliable than camera+ocr<br />
*though, bluetooth-enabled readers are already available.<br />
<br />
===Light Sensor===<br />
Ability to sense ambient light, and act accordingly. i.e if it's 3am and LightValue<.1 then Ring Quietly.<br />
<br />
===Wheel===<br />
A navigation wheel like on a sony/ericsson 810i would be nice.<br />
<br />
===Proximity Sensor===<br />
Switch off backlight when you place the phone to your ear. Prevent accidental activation of speakerphone or other sounds when the phone is near the ear (prevent hearing damage). Possibly switch the speakerphone on or off automatically depending on if the phone is by your head or not.<br />
<br />
=== Make ''all'' unlocking of phone, password protected===<br />
<br />
When my (current non-neophone) phone is in my pocket and I have it locked, it sometimes accidentally unlocks itself since only two keystrokes in the correct order are necessary to unlock it. When it's unlocked and still in my pocket it sometimes calls someone without my knowledge. All phones I've seen today have a press-just-one-button bypass to answer an incoming call even when the phone is locked. I suggest making the locking mechanism let the user configure it so that the user has to enter a password even for answering incoming calls. The likeliness of the phone accidentally runbbing against my car keys, hitting a ten character long password, unlocking the phone without my knowledge and consent is low enough even for us most unlucky users.<br />
<br />
==Expansion==<br />
===Positioning of Buttons, Connections and ports===<br />
<br />
Ideally any cable ports such as charging, USB, audio, docking should not get in the way of your hand or fingers when holding it in it's normal orientation. For the sake of SDIO cards an external SD slot should be on the top edge. IR for remote control software and ease of inter-device communication should be on the corner so that it is facing away from you for both orientations. Buttons obviously are positioned for finger control. An example of how '''not''' to do this would be the HTC Universal<br />
<br />
===Storage===<br />
<br />
====MMC/SD/SDIO slot (rather than?) miniSD or microSD====<br />
*Cheaper, more durable cards in a widely accepted format.<br />
*Much much larger storage capacity, [http://blog.scifi.com/tech/archives/2007/08/23/toshiba_unleash_1.html even 32GB]<br />
*Cards are harder to lose<br />
*Wider selection of accessories, including SDIO accessories.<br />
*Make externally available so that larger length SDIO cards can be used (thinking about SDIO WLAN here)<br />
*[http://en.wikipedia.org/wiki/Secure_Digital_card#SDHC SDHC] compatible. It seems to already have the right hardware for it - see [[Neo1973_Hardware#microSD-Card]].<br />
<br />
====Two SD slots====<br />
*Micro SDHC for /home partition. Keep like current design underneath SIM card<br />
*Hot swappable externally accessible normal size SDHC/SDIO slot<br />
<br />
===Local Communication===<br />
<br />
====USB====<br />
* 5V Powered, to avoid having to carry around a hub for when you want to occasionally plug in a memory stick. Many powered hubs will not recognize a totally unpowered host. Provide a maximum current to drive a basic USB keyboard/memory stick/mouse/webcam/astrowebcam. This could be done by adding a small cheap power converter like the [http://www.national.com/pf/LM/LM2753.html LM2753]<br />
* USB 2.0 <br />
* Standard type A socket for quick & easy insertion of memory sticks etc.<br />
* OTG (is this maybe supported already ?)<br />
* Bootable USB device emulation: the possibility to boot any computer on a bootable flagged partition of the transflash.<br />
* Protection against incorrectly wired USB ports: some USB ports are wired incorrectly; if the +5V and GND are swapped, the device would get -5V when it's expecting +5V, which could burn some chips. A reverse-biased diode between +5V and GND, D+ and GND, D- and GND, and (if used) ID and GND, with a low enough forward voltage drop (to limite the negative voltages to what the chips can withstand), would protect the device by tripping the port's short circuit protection.<br />
<br />
====Wireless USB support====<br />
[http://en.wikipedia.org/wiki/Wireless_USB Wireless USB] is the wireless version of USB offering data-rates up to 480 Mbit/s over short distances (<3 meter). Chipsets suitable for a phone are likely to take some time to be available.<br />
<br />
====SIR/FIR transceiver (Serial Infrared) / IR remote control====<br />
*An infrared transceiver is cheap, small, and useful for sync with many laptops and mobile phones. <br />
*Replace/emulate all IR-based remote controls used for your tv, vcr, etc on your neo cell phone.<br />
** replaces multiple 'dumb' devices with a single intelligent device (your neo) that you will probably carry with you at all times anyway. <br />
**Command sets should be retrieved from a database or learned from other less intelligent remote control devices with macros. <br />
**reduces clutter, particularly in the living room.<br />
**inceases the neo's practical status as an 'always-have' device. <br />
<br />
Other uses.<br />
*Detecting reflections from inside of a caddy, and switching from active mode.<br />
*FIR would be a nice option, as it's some 40 times faster than SIR.<br />
<br />
===Other===<br />
<br />
====Video Out====<br />
*Through a docking port<br />
**S-Video/Composite Out<br />
**DVI Out<br />
<br />
==Output devices==<br />
<br />
===LED===<br />
*The Neo1973 GTA02 will have LEDs of some sort behind at least one button. [http://lists.openmoko.org/pipermail/community/2007-July/008458.html]<br />
*A blinking LED would be a cheap, low power way to inform the user of new SMS/Email....<br />
**An alternative to this would be for one small part of the LCD to be separately backlit.<br />
**This requires the CPU and LCD to be somewhat active, to keep the LCD refreshed, but gives much more information.<br />
**A Small OLED Screen could be used and display much more information than a LED with minimal power usage.<br />
<br />
*For example a multicolor LED which pulses yellow for GSM/GPRS transmit, blue for Bluetooth/Wifi, green to indicate non-urgent information - missed call etc, red to indicate battery low or other urgent notices.<br />
<br />
**The LED and button ideas could be combined: illuminated buttons.<br />
**It must be possible to completely disable the LED to save power or other personal preferences.<br />
<br />
=== Flashlight ===<br />
For finding keys, or any other application. May also optionally pulse in time with ring, to make phone more visible.<br />
This is really well done in Nokia 5500.<br />
<br />
=== FM transmitter ===<br />
Small FM transmitter to output to car, and other nearby radios.<br />
<br />
===HAC Compliance===<br />
[http://quux.wiki.zoho.com/WhereAreHACphones.html Here] is some summary/discussion of how hearing aid compliance rules work in the US. Specifically it would be nice to see the phone include a [http://www.hearingresearch.org/Dr.Ross/telecoil_and_telephones.htm telecoil], which allows the phone to connect wirelessly to many standard hearing aids.<br />
<br />
==Mobile Communication options==<br />
<br />
===Generic Access Network / Unlicensed Mobile Access===<br />
This technology requires cooperation from the cellular provider, but [http://en.wikipedia.org/wiki/Unlicensed_Mobile_Access UMA/GAN] is already offered by T-Mobile in the United States, and perhaps others in other countries. Allowing the user to roam from GSM to wifi, this technology can save the end user a significant amount of money, and also allow the user to deploy coverage where there was none before. There are only a few UMA capable phones currently, but it would be great if this could be made to work on a phase 2 type OpenMoko device.<br />
<br />
Note that this features requires a more advanced access to the GSM modem. Special messages needs to be exchanged with the network.<br />
<br />
===Faster/better mobile connectivity.===<br />
[http://en.wikipedia.org/wiki/Gsm GSM]/[http://en.wikipedia.org/wiki/GPRS GPRS] is at best slow. An incremental improvement would be a radio with [http://en.wikipedia.org/wiki/EDGE EDGE ] support. EDGE is an evolved GSM standard and, like GPRS, it operates on the same frequency as voice. This means a quad-band EDGE radio will have near-complete worldwide coverage. <br />
<br />
[http://en.wikipedia.org/wiki/UMTS UMTS] - which is widespread in Europe and being deployed in the US, [http://en.wikipedia.org/wiki/HSDPA HSDPA] (asia) and any other mobile standards would be nice for faster data connectivity and coverage.<br />
It is unlikely that all of these will be supported initially, but it is a goal. These faster standards operate in different frequencies from GSM/GPRS/EDGE. Which frequency exactly will depend on the carrier and country. For UMTS in the US, AT&T uses 850/1900 MHz but T-Mobile will use 2100/1700 MHz for example.<br />
<br />
Until that goal is reached, it is likely that some phones will be brought out for various specific markets - Europe, Asia, US.<br />
<br />
===Ability to use multiple SIMs/networks===<br />
* External SIM sockets are widely available in China, a dual external socket would be a very good solution.<br />
* [http://www.fonefunshop.co.uk/dualsim/digital.htm Dual SIM card kit] - two SIMs are trimmed and combined, software supportwould be needed, and both can't be used at once...<br />
* Some networks support multiple numbers on one SIM. Unfortunately this won't allow split networks.<br />
* A second/dual GSM module would allow full use of both sims at all times.<br />
* As a hack, [http://wiki.openmoko.org/wiki/Wish_List#Bluetooth_powered_Multi-SIM_support use another mobile via BT].<br />
** As many as three SIM slots would be genuinely useful, especially for a 3G phone - some 3G data tariffs are only available on data-only SIMs. A user could quite reasonably have one SIM for data, once SIM for his personal voice calls, and a third SIM for his business number.<br />
<br />
===PMR446/FRS Radio===<br />
* Include a PMR/FRS Radio.<br />
* A two-way walkie talkie lets you use the phone to communicate with friends without requiring a GSM connection (crowded networks at festivals, at locations with no GSM coverage).<br />
<br />
===[[DECT]]===<br />
* Include a [[DECT]] GAP/CAT-iq transceiver so you can use your home and/or office PSTN line<br />
** Ability to use Alcatel phonebook stuff (like provided by the eventphone.de phone equipment) would be very nice too<br />
<br />
===[[SIP phone]]===<br />
Make stripped down (and thus cheaper) version of the Neo1973 phone for use as a SIP phone. Remove GPS, GSM, accelerometers, stilus.<br />
<br />
Addition of an centimeters-precise location system [http://en.wikipedia.org/wiki/Real_Time_Location_Systems RTLS] would be nice, as it will allow highly sensible indoor context detection. Image to put the phone next to your mirror (where you shave daily) and observe it automatically switch to news radio channel. Or put it next to your bed and see it automatically switch to "sleeping" mode, when only calls from predefined numbers are accepted.<br />
<br />
==Casing==<br />
See also: [[Alternate Neo1973 case designs]] for a list of cases being considered for design/manufacture by the community.<br />
<br />
===[[Expansion Back]]===<br />
* Replacement backs with additional features ranging from solar power, larger batteries, extra hardware, ...<br />
<br />
===Space efficient Lanyard===<br />
The hole at the bottom of the phone takes a lot of space. A [http://en.wikipedia.org/wiki/Kensington_Security_Slot Kensington Security Slot] could be used instead.<br />
<br />
=== Ruggedized version ===<br />
We need something you can drop from 4 feet in to a puddle of dirty water on construction site. Sunlight readable display. The big ugly pseudo military version.<br />
<br />
=== Transparent ===<br />
Make a transparent, see-through casing. Why do we need a closed casing for open hardware and open software? Show the world it is a truly Free/Open source phone.<br />
<br />
===[[Wishlist:Expansion Front|Expansion Front]]===<br />
Replacement fronts with e.g. extra buttons.<br />
<br />
<br />
<br />
==Misc==<br />
===Galileo/GLONASS/GPS receiver===<br />
*A multi-standard satellite positioning module would be nice eventually, it does not seem to be near-term due to chipset availability problems. Galileo is the to be launched (2011) European positioning system. GLONASS is the already existing Russian one.<br />
<br />
===X10 RF Remote===<br />
Many PC-based media centers are being equipped with an RF (433 MHz) / X10-based remote control. The [http://en.wikipedia.org/wiki/X10_(industry_standard) X10] protocol also facilitates home automation to control lamps, switches, etc.<br />
The advantages of using RF for control instead of Infra-red this that it also works when furniture, walls, or doors are blocking the path between RF remote and the equipment or device. [http://www.lirc.org/ Lirc] supports X10-based RF remotes (but expects having an USB RF receiver attached to the media center).<br />
<br />
===RFID tag/RFID Reader===<br />
* Implementation/Cooperation with: [http://www.rfidguardian.org/ RFID-Guardian]<br />
*An enable-able tag would be of use - for example being able to use the phone to open doors, or cars. Unfortunately, it's moderately hard to do secure programmable tags that are compatible with existing systems, for obvious reasons.<br />
* Say you have RFID tags on your personal belongings: cellphone, keys... Neo could be programmed to remember the last recorded GPS location before it lost contact with the respective RFIDs. It'd be trivial to check where you left your cellphone, get directions from a map...or beep when the phone gets out of RFID range.<br />
<br />
===Less weight===<br />
* Work on the weight of the Neo1973 and following devices. At the present time the Neo1973 is just a moderate / normal business or multimedia phone. The ordinary "user" may want something lighter. Take a look at the following table, that's the Neo1973 compared with other common bussiness or multimedia phones.<br />
{|border="1"<br />
| Neo1973 || Fujitsu-Siemens LOOX N560 || E-Ten Glofiish X500+ || Sony Ericsson P990i || iPhone || Nokia E65 <br />
|- <br />
| 184 g || 160 g || 146 g || 150 g || 135 g || 115 g <br />
|-<br />
|}<br />
<br />
===Make it smaller===<br />
* To stay within physical matters: Maybe the Neo1973 is also just a normal business/multimedia phone when looking at the size. It would be great the shrink it a bit. Especially the thickness of 18.5 mm could be worked on!<br />
<br />
===Standard 3.5mm headphone jack===<br />
The Neo1973 uses a 4-conductor 2.5mm jack for stereo headphones and a microphone. A 2.5mm jack is the most common for headsets. <br />
<br />
There is an emerging convention used in the Nokia N800 and some other devices. A 4-conductor 3.5mm jack that can use a microphone with special headsets, but can also be used with off-the-shelf 3.5mm stereo headphones. Adapters to 2.5mm are of course available and this 3.5mm jack is much more robust.<br />
<br />
Neglecting space limitations, multiple sockets - 2.5mm and 3.5mm would be nice. Probably not practical in a phone. Other expanded plugs might allow remote controls.<br />
<br />
Other uses might be better met using bluetooth, or USB audio.<br />
<br />
===Laser Pointer===<br />
Include a built in laser pointer. Everything is better with lasers.<br />
<br />
===Completely free hardware===<br />
Consider selling one device with absolutely no non-free components in it, even if that means dropping the GSM support. I believe having one such device available would be good, because then it could be recommended by organizations like the FSF which typically never recommends anything if it has even a little non-free code in it.<br />
<br />
=== Consider economy / inexpensive / less featured edition ===<br />
Some people want less features, because they do not need them. Leaving out some features either lets the phone get smaller or possibly enhances battery live.<br />
<br />
One big suggestion in this area is a b/w lower res display instead of the big color display.<br />
<br />
=== Inductive Charger ===<br />
<br />
It would be nice if it was possible to charge the phone without having to connect a cable. I'd like to have a simple docking station with an inductive charger like the type that's used for electric toothbrushes [http://home.howstuffworks.com/question292.htm ]. The charger itself could get its power from a standard wall-wart power supply, or it could be USB/Firewire powered.<br />
<br />
==Related Hardware==<br />
See [[Related Hardware]]<br />
<br />
[[Category:Hardware ideas| ]]<br />
[[Category:User]]</div>Bashttp://openmoko.org/wiki/Wish_List_-_HardwareWish List - Hardware2007-10-11T09:06:24Z<p>Bas: /* TV/radio receiver */</p>
<hr />
<div>This page details hardware features which some would like to go into future phones similar to the [[Neo1973]].<br />
<br />
Related pages are:<br />
*[[Wishlist - Hardware - Novel Devices]] - openmoko will run on a large number of devices in the future, some of which may be DVD players, cameras, or convergance devices. <br />
*[[Wishlist:Unlikely]] - Hardware that is unlikely to appear in any OpenMoko device, due to it being impossible to fabricate with near-term technology, or for other reasons.<br />
*[[Wishlist:Accessories]] - Accessories that people would like, that connect easily to the phone - initially primarily for the Neo1973 <br />
*[[Wishlist:Expansion]] - add-ons to the phone, maybe involving hardware changes, and software and hardware protocols to implement these.<br />
<br />
This page is rather long. Before adding a new idea, please read through this page and the above pages, to make sure your idea has not been suggested before.<br />
<br />
==Processor==<br />
===AT91CAP9S500A (ARM9 + FPGA-port)===<br />
Why FPGA?:<br />
*[http://hardware.silicon.com/servers/0,39024647,39166443,00.htm?r=1 20 March 2007 Green supercomputer is 'go' in Scotland] Quote: "...A supercomputer 10 times more energy efficient and up to 300 times faster than its traditional equivalents..."<br />
<br />
Take a look at this microcontroller, that integrates an ARM9 microcontroller and a dedicated FPGA port: AT91CAP9S500A. It has "only" a max. clock at 200MHz, but can use a FPGA for hardware acceleration, that could be used for video (de)compression, [http://en.wikipedia.org/wiki/AacPlus_v2 aacPlus v2]/[http://en.wikipedia.org/wiki/HE-AAC_v2 HE-AAC v2] sound (de)compression and many other things. HE-AAC v2 is better than [http://en.wikipedia.org/wiki/MP3 MP3].<br />
*[http://www.atmel.com/dyn/products/product_card.asp?family_id=689&family_name=AT91CAP+Microcontrollers&part_id=4137 AT91CAP9S500A] Quote: "...The AT91CAP9S500A is built around a 12-layer bus matrix, allowing a maximum internal bandwidth of twelve 32-bit buses. Its distributed DMA architecture enables multiple data transfers to take place between the processor, memories and peripherals with minimal processor overhead...".<br />
*[http://www.atmel.com/dyn/resources/prod_documents/doc6310.pdf GNU-Based Software Development on AT91SAM Microcontrollers]<br />
*Maybe this is a good tool?: [http://www.jhdl.org/ BYU JHDL, Open Source FPGA CAD Tools]<br />
*[http://www.eetimes.com/showArticle.jhtml;?articleID=197002705 02/05/2007, FPGA tool bottleneck stalls HPC] Quote: "...Current FPGA synthesis, placement and routing tools are written for hardware designers, not software programmers simply trying to accelerate an algorithm..."<br />
<br />
This seems to be a good hardware mix (ARM+FPGA). It does [http://en.wikipedia.org/wiki/Theora Ogg Theora] or [http://en.wikipedia.org/wiki/MJPEG MJPEG] in the FPGA with 1 million gates:<br />
*http://sourceforge.net/projects/elphel, [http://wiki.elphel.com/index.php?title=10353 board 10353], [http://wiki.elphel.com/index.php?title=Camera_hardware camera hardware], [http://wiki.elphel.com/index.php?title=Main_Page Main page], [http://www.elphel.com/articles/index.html Imaging solutions with Free software and open hardware]<br />
<br />
Just another FPGA+microcontroller example: <br />
*[http://melzer.ch/html/body_alya.html The Alya Project] ([http://home.nikocity.de/andymon/hfg/Alya/alya.html old page])<br />
*[http://melzer.ch/ALYA.ASM PIC assembler source code], [http://melzer.ch/ALYA.TDF Altera FPGA code]. Schematic: [http://melzer.ch/Schaltplan1.gif], [http://melzer.ch/Schaltplan2.gif], [http://melzer.ch/Schaltplan3.gif]<br />
<br />
I do not think this means what you think it means... I read "...and a metal programmable (MP) block of 500K gates of digital logic." as meaning that it's a one-time programmable block, more akin to a standard-cell ASIC than an FPGA. This is supported by the fact that their development board contains a separate FPGA chip. Now, granted, having a 500K gate ASIC on board an ARM is a cool thing... but not quite as cool as this chip appeared at first glance.<br />
<br />
===Samsung S3C2443===<br />
*[http://www.samsung.com/global/business/semiconductor/productInfo.do?fmly_id=229&partnum=S3C2443&&ppmi=1427 Samsung S3C2443] Up to 533 MHz, USB 2.0<br />
<br />
==Possible FPGA==<br />
This FPGA is just an example:<br />
*[http://www.xilinx.com/products/silicon_solutions/fpgas/spartan_series/spartan3an_fpgas/capabilities/index.htm Spartan-3AN FPGA Capabilities] Quote: "...Simple and secure embedded application storage with up to 11Mb of integrated user Flash...Enable simple arithmetic and math functions as well as advanced DSP functions to derive over 330 Giga MACs/sec...Up to 32 18 x 18 embedded multipliers support 18-bit signed or 17-bit unsigned multiplication, and can be cascaded to support wider bits..."<br />
**XC3S1400AN-4FGG676CES $91<br />
**XC3S200AN-4FTG256CES $25.87<br />
<br />
====Tool for FPGAs====<br />
*[http://www.xilinx.com/ise/logic_design_prod/webpack.htm xilinx.com: ISE WebPACK is the industry´s only FREE, fully featured front-to-back FPGA design solution for Linux, Windows XP, and Windows Vista]<br />
<br />
===Asynchronous FPGA, AFPGA===<br />
*[http://www.achronix.com/products.html Achronix-ULTRA]<br />
**[http://www.pldesignline.com/news/186700955 Achronix preps 2-GHz Asynchronous FPGA for sampling in 2007]<br />
**[http://vlsi.cornell.edu/fpga.php Asynchronous VLSI and Architecture, Cornell University: Asynchronous Field-Programmable Gate Arrays (AFPGAs)] Quote: "...integrated pipelining support..."<br />
**[http://citeseer.ist.psu.edu/teifel03programmable.html Programmable Asynchronous Pipeline Arrays (2003) John Teifel, Rajit Manohar]<br />
<br />
==Internal Memory==<br />
===RAM===<br />
128MB Dedicated for open files, running software etc., not for storage, or 256MB at all would be really nice and enough for any future software.<br />
<br />
===ROM===<br />
Enough to Hold O/S and a fair number of applications and their settings. Persistent Storage with XIP capability. About 128 MB.<br />
<br />
===Storage===<br />
An internal Micro SDHC should be used for users' files and additional software<br />
<br />
==Wireless data networking==<br />
<br />
===WiMAX support===<br />
[http://en.wikipedia.org/wiki/Wimax WiMAX] is a high-speed data service, similar to wifi, though longer range and newer. Where service is available, this would complement WiFi. Unfortunately, unlike wifi, frequencies vary worldwide, so global usage may be complex.<br />
<br />
===Emerging Protocols===<br />
*[http://en.wikipedia.org/wiki/Near_Field_Communication Near Field Communication] has a few centimeter range, useable for keys, ID badges, pairing bluetooth devices and similar uses. Mentioned in newer bluetooth and SD standards. (No products.)<br />
*[http://en.wikipedia.org/wiki/ZigBee ZigBee] is designed for connecting sensors and switches in buildings, with many options including mesh networks and aggressive power saving compared to bluetooth. (Almost no products available.)<br />
*The [http://en.wikipedia.org/wiki/ANT_%28network%29 ANT network] is for connecting worn devices. Similar to ZigBee, but much simpler and maybe lower power. ([http://www.thisisant.com/?section=9 Short list] of products.)<br />
<br />
==Camera==<br />
<br />
* A camera that can take reasonable quality video and pictures is something many want. Applications vary from simple snapping, to gesture interfaces, video conferencing, barcode reading, buisness card reading, healthcare, servicing, and more.<br />
<br />
* Some people can't take cameras into work - a model without the camera, or some way of removing the camera would be useful or leave the camera chip in place and have a removable lens assembly and replacement backcover.<br />
<br />
* See [[Wishlist:Camera]] for a more detailed wishlist.<br />
<br />
==Display==<br />
===Multitouch screen===<br />
<br />
''Main article: [[Wishlist:Spell_weaving|Spell weaving]]''<br />
<br />
See also [http://pogue.blogs.nytimes.com/2007/03/27/the-multi-touch-screen/ this page] containing a link to a video demonstration.<br />
<br />
A history of multitouch implementations is [http://billbuxton.com/multitouchOverview.html here] ([http://google.com/search?q=cache:billbuxton.com/multitouchOverview.html google cache version])<br />
<br />
*Use examples: [http://www.youtube.com/watch?v=UcKqyn-gUbY&mode=related&search= Multi-touch interface (from Adobe TED)], [http://www.youtube.com/watch?v=1ftJhDBZqss&mode=related&search= Multi Touch (new touchscreen technology)]<br />
<br />
===Bigger and better screen===<br />
2.8" widescreen (like in [http://etencorp.com E-ten] PDA/smartphones), or 3.5" widescreen (like in [http://www.expansys.ie/d.aspx?i=134944 Fujitsu Siemens LOOX N560]).<br />
<br />
262k or 16.7M colurs for displaying images and especially videos.<br />
<br />
OLED for better contrast, more rich colours, and less energy consumption.<br />
<br />
Maybe the [http://www.sharpsme.com/Page.aspx/europe/en/part/LS037V7DW01/ LS037V7DW01] by Sharp could be a solution. It has nearly the same specs as the currently used, but 3,7" -- [[User:Wedge | Wedge]]<br />
<br />
===Distance sensing touchscreen===<br />
{{Main|Hardware:NearlyTouchScreen}}<br />
TouchKo's (now Wacom Company Ltd.) spatial capacitive "touchscreen", can sense fingers at a small distance, so you do not get your display greasy, and can unlike some touchscreens, be operated with gloves.<br />
<br />
===<s>Video acceleration</s>===<br />
Hardware acceleration for video playback and 2D/3D accelleration will be present in [[Neo1973 GTA02]].<br />
<br />
===EPD===<br />
Or electronic paper display, EPD is used in many new devices such as the new Motorola motofone, sonys new e-reader and Irex's iliad. The technology provides thin, lightweight, power saving screens using new eink technology. This technology could cut the weight of the phone and its power usage. For more info see: [http://www.eink.com eink's website].<br />
<br />
Pro: laserprinter like quality, glossy, very stable image, easy on the eyes. Electronics are similar to TFT. Very low power consumption. <br />
<br />
Con: Black and grey only (like a newspaper, but glossy), although there were already color prototypes in 2005. low framerate (5fps). Can reflect light (like paper), backlight is impossible.<br />
<br />
===Transreflective===<br />
It would be nice to have (the option of) a transreflective display, which while being less bright, is readable without needing to power the backlight. Then again, it depends on how much power the backlight uses compared to everything else...<br />
<br />
==="Slightly" Larger Screen===<br />
43mm x 57mm (2.8inch diagonal) is tiny. A 53mm x 71mm (3.5 inch diagonal) like on the TD035STEE1 would be a nice improvement. A widescreen format at about 53mm x 82.5mm instead of the 3:4 aspect ratio would be even cooler (if one could be found).<br />
<br />
===Second Display===<br />
A 32x32 OLED display possibly on the back for camera framing or on an edge so it can be viewed like a pager.<br />
This could be used to display any number of alerts (from any installed software) the alerts could have a dynamic prioritisation which means during the work day a message from the boss has high priority but lower at home (could be GPS/Time controlled?) multiple alerts shrink the icons to a 3x3 grid higher priority messages get more space.<br />
<br />
==Input devices==<br />
<br />
===No Dependence on Stylus===<br />
The Neo's basic functionality should be completely usable without a stylus, Like the iPhone but with stylus use for precision work.<br />
<br />
===A laser projection keyboard===<br />
Similar to [http://www.thinkgeek.com/computing/input/8193/ this], except the device would be integrated into the phone itself. Setting the Neo up on a stand on a flat surface (perhaps a stand could be built into the back of the Neo itself, or into a case) would turn the Neo into a micro-laptop. There may be several issues with the inclusion of this technology, including patents, the space required to project the laser grids, and the power consumption. If possible, however, it would make text input a breeze.<br />
<br />
===Just a few more Buttons===<br />
<br />
2 buttons more, 3 buttons total, mounted sideways would be enough. You could use them for play/pause and loudness controll while the phone remains in your pocket (display locked, ...), reading mails, rss, ebooks,... without wasting display space and so on.<br />
<br />
With 5 buttons in total you could possibly emulate a keyboard (2^5 = 32 combinations) for those who know how to play a flute. Useable onehanded, not wasting display space and faster than t9. (It's not faster than T9 - I've used this system with the microwriter agenda --[[User:Speedevil|Speedevil]] 00:00, 2 July 2007 (CEST)) Hopefully this is not patented already.<br />
<br />
===D-Pad and Buttons===<br />
*Adding a D-pad (to the bottom of the phone) and 2 to 4 buttons (to the top) would provide some tactile input controls, in addition to the touchscreen. They could be used as shortcut keys in the menu, or playback control when playing media. When the phone is held sideways, they can be used as games controls. (With touchscreen alone, gameplay options are limited)<br />
<br />
Game buttons would be best on both sides of the screen. The larger the buttons, the better. 2x 4 buttons in up-down-left-right configuration + some extra buttons separately a bit lower on the device would be good for many for emulation games. <br />
<br />
Here is a concept drawing of a possible neo1973 gaming version: <br />
(This has a 4-way direction pad, 8 way may be better for gaming)<br />
<br/><br />
[[Image:Neogame90.jpg]]<br />
<br/><br />
Shoulder buttons would be a great addition, too. It would be interesting if there was a total 4 of them, one for every corner. It would make the phone very flexible for rotating and 2 to 6 players playing on one device.<br />
<br/><br />
:''Note'' : The [http://en.wikipedia.org/wiki/Tapwave_Zodiac Tapwave Zodiac] Palm PDA / Game console hybrid had a similar setup - with an analog stick on the left (also used for quick selection using a radial main menu when working as a PDA), 4 buttons on the right (also configurable for shortcuts when using the device as PDA), and 2 shoulder buttons. Also it had and still has an enthusiastic scene of homebrew development (almost any console emulator for PalmOS can also take advantage of the additional buttons and graphic power of the device). If we also take into account the success encountered by the [http://en.wikipedia.org/wiki/GP32 GP32] in the past and the [http://en.wikipedia.org/wiki/GP2X GP2X] currently on the homebrew scene, it's not unreasonable to plan a future OpenMoko device with both a SmartPhone/PDA functionnality ''and'' hand-held console targeting homebrew development.<br />
<br />
===Thumb keyboard or keyboard attachment accessory===<br />
*Could be slide out or clamshell (hinge on long side) design with an external OLED. The keyboard should be protected when not in use.<br />
*Could be a clip on keyboard that attaches to the serial port or communicates by bluetooth (not preferred for permanent keyboard users).<br />
*Cheap clippable miniusb keyboard<br />
*One of the layouts proposed in [[Hardware:Keyboards]]<br />
* What about virtual keyboard? [[http://www.extremetech.com/article2/0,3973,539778,00.asp Keyboard]]<br />
<br />
===Analogue Controllers===<br />
<br />
====Trackball====<br />
A trackball would provide an efficient mouse-like interface in a very compact package. As exemplified in the newer Blackberry&reg; models.<br />
Maybe instead an optical sensor as are used in mice could be used so that the whole phone can be moved over a surface just like a mouse. (It could function as a Bluetooth mouse for other devices like laptop computers: see [[Bluetooth_Support#Acting_as_HID_device]]. Adding one other two-axis analogue input (possibly just the screen) would make the Neo usable as a TrackPoint or scroll-and-tilt mouse.) The same sensor might be usable as a barcode reader.<br />
<br />
====Analog Joystick====<br />
A joystick, or [http://www.extremetech.com/article2/0,1697,1772689,00.asp Rollermouse]-like device would provide additional control, compared with touchscreen only.<br />
*A standard [http://en.wikipedia.org/wiki/Pointing_stick pointing stick (ie. TrackPoint)] might serve well. As a fairly standard part, might they be quite inexpensive?<br />
<br />
====Dual analogues====<br />
Dual analogue controllers (one trackball or joystick above, one below the screen, most likely) might even be feasible. That might be overkill since the accelerometers or touchscreen can be used to provide a second analogue input. But it would be nice to have four axes of analogue control without having to tilt the screen away from you or partly cover it with your hand.<br />
<br />
===TV/radio receiver===<br />
[[Digital Television]], [[Digital Radio]] or even normal analogue TV/radio is widely available in the world, though unfortunately in various different forms. In markets where one standard is widespread, and hardware is suitable, it would be a great extension of the phone to a general entertainment device for when you're away from home. Multi standard devices would be ideal, but may not be small, low-power, or cheap.<br />
A good start would be an FM receiver, since it's one of the most widely used formats of radio broadcasting in the world.<br />
<br />
===Accelerometer=== <br />
This enables the phone to sense which direction 'down' is, and to sense any movements the phone makes.<br />
<br />
See [[Accelerometer Fundamentals]] for more information on accelerometers as they may be used in phones.<br />
<br />
In some cases integrated gyroscopes may also be needed. A [[#Digital compass]] can even be of more use since it gives absolute rotation so slow rotations could also be measured. A 3D compass would be nicest, but a simple 2D compass already is a helpful addition to the accelerometers.<br />
<br />
*[[Wishlist:3D Viewport|3D Viewport]]<br />
*[[Wishlist:Computer Mouse|Computer Mouse]]<br />
*[[Wishlist:Determine Position|Determine Position]]<br />
*[[Wishlist:Dynamic Screen Orientation|Dynamic Screen Orientation]]<br />
*Change media player playlist when jogging vs walking. <br />
*Attempt to use to stabilise any future camera.<br />
<br />
This feature is scheduled for inclusion in the phase 2 Neo1973, currently slated for release in October 2007.<br />
<br />
===Side-Mounted Touch Strip===<br />
Add a "touch strip" sensor onto the side of the phone which can be used to scroll. By having it on the side you can use your thumb to scroll comfortably while holding the phone one-handed. An 8-element capacitive sensor would work wonderfully and be easy to fab using either a Quantum QT411 (http://www.qprox.com/products/qslide_qt411.php) or Analog Devices AD7143 (http://www.analog.com/en/prod/0,2877,AD7143,00.html) controller. The Analog Devices chip seems better suited due to it's smaller allowable element size.<br />
*With the AD7143 you can have an 8-element (128-position) 25mm long strip - Perfect!.<br />
*With a few OLED screens beneath the strip it could be used as dynamic configurable buttons/alerts eg. zoom/flash/shutter with a camera application and SMS/Email/Voicemail alerts in standby<br />
<br />
<br />
:Maybe it would be also possible to use is as finger print reader? --[[User:Tolein|tolein]] 20:18, 1 October 2007 (GMT+1)<br />
<br />
===Heart Rate Compatibility=== <br />
<br />
An RF interface to receive data from popular heart rate straps (Polar, Garmin, Sigma, Suunto, etc.). This would go along well with the existing GPS functionality and possible future Accelerometer functionality to make for a full-blown workout tool.<br />
<br />
Software can be written to track heart rate along a running, cycling, skiing, swimming loop, to monitor max and min heart rate, to match heart rate data to GPS coordinates and print map data w/ relevant data.<br />
<br />
===Digital compass=== <br />
A digital compass is useful for orienting maps to the terrain and other location/direction/orientation based applications (... is 300 meter that way) when the user is standing still (regardless of GPS reception) and for following a bearing when GPS reception is poor or speed is low. Also could be used to make the accelerometer data more exact.<br />
<br />
Very small [[I2C]] sensors like [http://www.ssec.honeywell.com/magnetic/hmc6352.html Honeywell's HMC6352 2-Axis Digital Integrated Compass] (6.5 x 6.5 x 1.5 mm) are very appropriate for this.<br />
<br />
*[[Wishlist:Auto Align Map]]<br />
<br />
See [[Wishlist - Hardware: Digital compass]] for more information<br />
<br />
===Thermometer===<br />
An electronic thermometer might become handy for some users.<br />
<br />
There are very small [[I2C]] devices available, that could easily integrate to the existing bus. For example [http://focus.ti.com/docs/prod/folders/print/tmp100.html this one from ti].<br />
(Could just be cheap and use the thermometer from the battery, thats how they did it in the nokia 5140's). Also is integrated in a barometer/altimeter like the SMD500 mentioned in [[Wish List - Hardware - Atmospheric]].<br />
<br />
===Barometer and Variometer (Altimeter)===<br />
<br />
A Barometer measures air pressure. This can be used to give weather information, and also as a variometer, to sense relative altitude. Variometers are commonly used in flying microlight and ultralight aircraft, to get accurate relative altitude.<br />
<br />
These are also common on high end GPS units. This is a great feature for walkers as you can tell how far you have got on any accent/decent.<br />
<br />
See [[Wish List - Hardware - Atmospheric]] for more information.<br />
<br />
===Finger print sensor===<br />
A fingerprint sensor gives easy and fast access to the phone, could lock the touchscreen etc. An example of this device can be found at [http://www.sonystyle.com/is-bin/INTERSHOP.enfinity/eCS/Store/en/-/USD/SY_BrowseCatalog-Start?CategoryName=cpu_VAIONotebookComputers_UX_Series&Dept=computers Sony UX17].<br />
<br />
Most fingerprint sensors in the embedded market include a navigation mode, where they work similar to either a touch-stick or touch-pad of a laptop.<br />
<br />
===Barcode Scanner===<br />
*less cpu intensive and more reliable than camera+ocr<br />
*though, bluetooth-enabled readers are already available.<br />
<br />
===Light Sensor===<br />
Ability to sense ambient light, and act accordingly. i.e if it's 3am and LightValue<.1 then Ring Quietly.<br />
<br />
===Wheel===<br />
A navigation wheel like on a sony/ericsson 810i would be nice.<br />
<br />
===Proximity Sensor===<br />
Switch off backlight when you place the phone to your ear. Prevent accidental activation of speakerphone or other sounds when the phone is near the ear (prevent hearing damage). Possibly switch the speakerphone on or off automatically depending on if the phone is by your head or not.<br />
<br />
=== Make ''all'' unlocking of phone, password protected===<br />
<br />
When my (current non-neophone) phone is in my pocket and I have it locked, it sometimes accidentally unlocks itself since only two keystrokes in the correct order are necessary to unlock it. When it's unlocked and still in my pocket it sometimes calls someone without my knowledge. All phones I've seen today have a press-just-one-button bypass to answer an incoming call even when the phone is locked. I suggest making the locking mechanism let the user configure it so that the user has to enter a password even for answering incoming calls. The likeliness of the phone accidentally runbbing against my car keys, hitting a ten character long password, unlocking the phone without my knowledge and consent is low enough even for us most unlucky users.<br />
<br />
==Expansion==<br />
===Positioning of Buttons, Connections and ports===<br />
<br />
Ideally any cable ports such as charging, USB, audio, docking should not get in the way of your hand or fingers when holding it in it's normal orientation. For the sake of SDIO cards an external SD slot should be on the top edge. IR for remote control software and ease of inter-device communication should be on the corner so that it is facing away from you for both orientations. Buttons obviously are positioned for finger control. An example of how '''not''' to do this would be the HTC Universal<br />
<br />
===Storage===<br />
<br />
====MMC/SD/SDIO slot (rather than?) miniSD or microSD====<br />
*Cheaper, more durable cards in a widely accepted format.<br />
*Much much larger storage capacity, [http://blog.scifi.com/tech/archives/2007/08/23/toshiba_unleash_1.html even 32GB]<br />
*Cards are harder to lose<br />
*Wider selection of accessories, including SDIO accessories.<br />
*Make externally available so that larger length SDIO cards can be used (thinking about SDIO WLAN here)<br />
*[http://en.wikipedia.org/wiki/Secure_Digital_card#SDHC SDHC] compatible. It seems to already have the right hardware for it - see [[Neo1973_Hardware#microSD-Card]].<br />
<br />
====Two SD slots====<br />
*Micro SDHC for /home partition. Keep like current design underneath SIM card<br />
*Hot swappable externally accessible normal size SDHC/SDIO slot<br />
<br />
===Local Communication===<br />
<br />
====USB====<br />
* 5V Powered, to avoid having to carry around a hub for when you want to occasionally plug in a memory stick. Many powered hubs will not recognize a totally unpowered host. Provide a maximum current to drive a basic USB keyboard/memory stick/mouse/webcam/astrowebcam. This could be done by adding a small cheap power converter like the [http://www.national.com/pf/LM/LM2753.html LM2753]<br />
* USB 2.0 <br />
* Standard type A socket for quick & easy insertion of memory sticks etc.<br />
* OTG (is this maybe supported already ?)<br />
* Bootable USB device emulation: the possibility to boot any computer on a bootable flagged partition of the transflash.<br />
* Protection against incorrectly wired USB ports: some USB ports are wired incorrectly; if the +5V and GND are swapped, the device would get -5V when it's expecting +5V, which could burn some chips. A reverse-biased diode between +5V and GND, D+ and GND, D- and GND, and (if used) ID and GND, with a low enough forward voltage drop (to limite the negative voltages to what the chips can withstand), would protect the device by tripping the port's short circuit protection.<br />
<br />
====Wireless USB support====<br />
[http://en.wikipedia.org/wiki/Wireless_USB Wireless USB] is the wireless version of USB offering data-rates up to 480 Mbit/s over short distances (<3 meter). Chipsets suitable for a phone are likely to take some time to be available.<br />
<br />
====SIR/FIR transceiver (Serial Infrared) / IR remote control====<br />
*An infrared transceiver is cheap, small, and useful for sync with many laptops and mobile phones. <br />
*Replace/emulate all IR-based remote controls used for your tv, vcr, etc on your neo cell phone.<br />
** replaces multiple 'dumb' devices with a single intelligent device (your neo) that you will probably carry with you at all times anyway. <br />
**Command sets should be retrieved from a database or learned from other less intelligent remote control devices with macros. <br />
**reduces clutter, particularly in the living room.<br />
**inceases the neo's practical status as an 'always-have' device. <br />
<br />
Other uses.<br />
*Detecting reflections from inside of a caddy, and switching from active mode.<br />
*FIR would be a nice option, as it's some 40 times faster than SIR.<br />
<br />
===Other===<br />
<br />
====Video Out====<br />
*Through a docking port<br />
**S-Video/Composite Out<br />
**DVI Out<br />
<br />
==Output devices==<br />
<br />
===LED===<br />
*The Neo1973 GTA02 will have LEDs of some sort behind at least one button. [http://lists.openmoko.org/pipermail/community/2007-July/008458.html]<br />
*A blinking LED would be a cheap, low power way to inform the user of new SMS/Email....<br />
**An alternative to this would be for one small part of the LCD to be separately backlit.<br />
**This requires the CPU and LCD to be somewhat active, to keep the LCD refreshed, but gives much more information.<br />
**A Small OLED Screen could be used and display much more information than a LED with minimal power usage.<br />
<br />
*For example a multicolor LED which pulses yellow for GSM/GPRS transmit, blue for Bluetooth/Wifi, green to indicate non-urgent information - missed call etc, red to indicate battery low or other urgent notices.<br />
<br />
**The LED and button ideas could be combined: illuminated buttons.<br />
**It must be possible to completely disable the LED to save power or other personal preferences.<br />
<br />
=== Flashlight ===<br />
For finding keys, or any other application. May also optionally pulse in time with ring, to make phone more visible.<br />
This is really well done in Nokia 5500.<br />
<br />
=== FM transmitter ===<br />
Small FM transmitter to output to car, and other nearby radios.<br />
<br />
===HAC Compliance===<br />
[http://quux.wiki.zoho.com/WhereAreHACphones.html Here] is some summary/discussion of how hearing aid compliance rules work in the US. Specifically it would be nice to see the phone include a [http://www.hearingresearch.org/Dr.Ross/telecoil_and_telephones.htm telecoil], which allows the phone to connect wirelessly to many standard hearing aids.<br />
<br />
==Mobile Communication options==<br />
<br />
===Generic Access Network / Unlicensed Mobile Access===<br />
This technology requires cooperation from the cellular provider, but [http://en.wikipedia.org/wiki/Unlicensed_Mobile_Access UMA/GAN] is already offered by T-Mobile in the United States, and perhaps others in other countries. Allowing the user to roam from GSM to wifi, this technology can save the end user a significant amount of money, and also allow the user to deploy coverage where there was none before. There are only a few UMA capable phones currently, but it would be great if this could be made to work on a phase 2 type OpenMoko device.<br />
<br />
Note that this features requires a more advanced access to the GSM modem. Special messages needs to be exchanged with the network.<br />
<br />
===Faster/better mobile connectivity.===<br />
[http://en.wikipedia.org/wiki/Gsm GSM]/[http://en.wikipedia.org/wiki/GPRS GPRS] is at best slow. An incremental improvement would be a radio with [http://en.wikipedia.org/wiki/EDGE EDGE ] support. EDGE is an evolved GSM standard and, like GPRS, it operates on the same frequency as voice. This means a quad-band EDGE radio will have near-complete worldwide coverage. <br />
<br />
[http://en.wikipedia.org/wiki/UMTS UMTS] - which is widespread in Europe and being deployed in the US, [http://en.wikipedia.org/wiki/HSDPA HSDPA] (asia) and any other mobile standards would be nice for faster data connectivity and coverage.<br />
It is unlikely that all of these will be supported initially, but it is a goal. These faster standards operate in different frequencies from GSM/GPRS/EDGE. Which frequency exactly will depend on the carrier and country. For UMTS in the US, AT&T uses 850/1900 MHz but T-Mobile will use 2100/1700 MHz for example.<br />
<br />
Until that goal is reached, it is likely that some phones will be brought out for various specific markets - Europe, Asia, US.<br />
<br />
===Ability to use multiple SIMs/networks===<br />
* External SIM sockets are widely available in China, a dual external socket would be a very good solution.<br />
* [http://www.fonefunshop.co.uk/dualsim/digital.htm Dual SIM card kit] - two SIMs are trimmed and combined, software supportwould be needed, and both can't be used at once...<br />
* Some networks support multiple numbers on one SIM. Unfortunately this won't allow split networks.<br />
* A second/dual GSM module would allow full use of both sims at all times.<br />
* As a hack, [http://wiki.openmoko.org/wiki/Wish_List#Bluetooth_powered_Multi-SIM_support use another mobile via BT].<br />
** As many as three SIM slots would be genuinely useful, especially for a 3G phone - some 3G data tariffs are only available on data-only SIMs. A user could quite reasonably have one SIM for data, once SIM for his personal voice calls, and a third SIM for his business number.<br />
<br />
===PMR446/FRS Radio===<br />
* Include a PMR/FRS Radio.<br />
* A two-way walkie talkie lets you use the phone to communicate with friends without requiring a GSM connection (crowded networks at festivals, at locations with no GSM coverage).<br />
<br />
===[[DECT]]===<br />
* Include a [[DECT]] GAP/CAT-iq transceiver so you can use your home and/or office PSTN line<br />
** Ability to use Alcatel phonebook stuff (like provided by the eventphone.de phone equipment) would be very nice too<br />
<br />
===[[SIP phone]]===<br />
Make stripped down (and thus cheaper) version of the Neo1973 phone for use as a SIP phone. Remove GPS, GSM, accelerometers, stilus.<br />
<br />
Addition of an centimeters-precise location system [http://en.wikipedia.org/wiki/Real_Time_Location_Systems RTLS] would be nice, as it will allow highly sensible indoor context detection. Image to put the phone next to your mirror (where you shave daily) and observe it automatically switch to news radio channel. Or put it next to your bed and see it automatically switch to "sleeping" mode, when only calls from predefined numbers are accepted.<br />
<br />
==Casing==<br />
See also: [[Alternate Neo1973 case designs]] for a list of cases being considered for design/manufacture by the community.<br />
<br />
===[[Expansion Back]]===<br />
* Replacement backs with additional features ranging from solar power, larger batteries, extra hardware, ...<br />
<br />
===Space efficient Lanyard===<br />
The hole at the bottom of the phone takes a lot of space. A [http://en.wikipedia.org/wiki/Kensington_Security_Slot Kensington Security Slot] could be used instead.<br />
<br />
=== Ruggedized version ===<br />
We need something you can drop from 4 feet in to a puddle of dirty water on construction site. Sunlight readable display. The big ugly pseudo military version.<br />
<br />
=== Transparent ===<br />
Make a transparent, see-through casing. Why do we need a closed casing for open hardware and open software? Show the world it is a truly Free/Open source phone.<br />
<br />
===[[Wishlist:Expansion Front|Expansion Front]]===<br />
Replacement fronts with e.g. extra buttons.<br />
<br />
<br />
<br />
==Misc==<br />
===Galileo/GLONASS/GPS receiver===<br />
*A multi-standard satellite positioning module would be nice eventually, it does not seem to be near-term due to chipset availability problems. Galileo is the to be launched (2011) European positioning system. GLONASS is the already existing Russian one.<br />
<br />
===X10 RF Remote===<br />
Many PC-based media centers are being equipped with an RF (433 MHz) / X10-based remote control. The [http://en.wikipedia.org/wiki/X10_(industry_standard) X10] protocol also facilitates home automation to control lamps, switches, etc.<br />
The advantages of using RF for control instead of Infra-red this that it also works when furniture, walls, or doors are blocking the path between RF remote and the equipment or device. [http://www.lirc.org/ Lirc] supports X10-based RF remotes (but expects having an USB RF receiver attached to the media center).<br />
<br />
===RFID tag/RFID Reader===<br />
* Implementation/Cooperation with: [http://www.rfidguardian.org/ RFID-Guardian]<br />
*An enable-able tag would be of use - for example being able to use the phone to open doors, or cars. Unfortunately, it's moderately hard to do secure programmable tags that are compatible with existing systems, for obvious reasons.<br />
* Say you have RFID tags on your personal belongings: cellphone, keys... Neo could be programmed to remember the last recorded GPS location before it lost contact with the respective RFIDs. It'd be trivial to check where you left your cellphone, get directions from a map...or beep when the phone gets out of RFID range.<br />
<br />
===Less weight===<br />
* Work on the weight of the Neo1973 and following devices. At the present time the Neo1973 is just a moderate / normal business or multimedia phone. The ordinary "user" may want something lighter. Take a look at the following table, that's the Neo1973 compared with other common bussiness or multimedia phones.<br />
{|border="1"<br />
| Neo1973 || Fujitsu-Siemens LOOX N560 || E-Ten Glofiish X500+ || Sony Ericsson P990i || iPhone || Nokia E65 <br />
|- <br />
| 184 g || 160 g || 146 g || 150 g || 135 g || 115 g <br />
|-<br />
|}<br />
<br />
===Make it smaller===<br />
* To stay within physical matters: Maybe the Neo1973 is also just a normal business/multimedia phone when looking at the size. It would be great the shrink it a bit. Especially the thickness of 18.5 mm could be worked on!<br />
<br />
===Standard 3.5mm headphone jack===<br />
The Neo1973 uses a 4-conductor 2.5mm jack for stereo headphones and a microphone. A 2.5mm jack is the most common for headsets. <br />
<br />
There is an emerging convention used in the Nokia N800 and some other devices. A 4-conductor 3.5mm jack that can use a microphone with special headsets, but can also be used with off-the-shelf 3.5mm stereo headphones. Adapters to 2.5mm are of course available and this 3.5mm jack is much more robust.<br />
<br />
Neglecting space limitations, multiple sockets - 2.5mm and 3.5mm would be nice. Probably not practical in a phone. Other expanded plugs might allow remote controls.<br />
<br />
Other uses might be better met using bluetooth, or USB audio.<br />
<br />
===Laser Pointer===<br />
Include a built in laser pointer. Everything is better with lasers.<br />
<br />
===Completely free hardware===<br />
Consider selling one device with absolutely no non-free components in it, even if that means dropping the GSM support. I believe having one such device available would be good, because then it could be recommended by organizations like the FSF which typically never recommends anything if it has even a little non-free code in it.<br />
<br />
=== Consider economy / inexpensive / less featured edition ===<br />
Some people want less features, because they do not need them. Leaving out some features either lets the phone get smaller or possibly enhances battery live.<br />
<br />
One big suggestion in this area is a b/w lower res display instead of the big color display.<br />
<br />
=== Inductive Charger ===<br />
<br />
It would be nice if it was possible to charge the phone without having to connect a cable. I'd like to have a simple docking station with an inductive charger like the type that's used for electric toothbrushes [http://home.howstuffworks.com/question292.htm ]. The charger itself could get its power from a standard wall-wart power supply, or it could be USB/Firewire powered.<br />
<br />
==Related Hardware==<br />
See [[Related Hardware]]<br />
<br />
[[Category:Hardware ideas| ]]<br />
[[Category:User]]</div>Bashttp://openmoko.org/wiki/IPhoneIPhone2007-10-08T08:42:01Z<p>Bas: /* Comparison between Apple iPhone and the "Open Source iPhone" Neo1973 (GTA02) running OpenMoko Linux */</p>
<hr />
<div>== Comparison between Apple iPhone and the "Open Source iPhone" Neo1973 ([[GTA02#.22Phase_2.22_.28GTA02.2C_.22Mass_Market.22.29|GTA02]]) running OpenMoko Linux ==<br />
{{Note|The Neo1973 revision this page is about is the [[GTA02#.22Phase_2.22_.28GTA02.2C_.22Mass_Market.22.29|GTA02]]-revision that is announced for October 2007. For the earlier Neo1973 revision see [[IPhone_(GTA01)]]}}<br />
Apple announced their [http://www.apple.com/iphone/technology/specs.html iPhone] at MacWorld 2007. It is fairly similar to the [http://lists.openmoko.org/pipermail/community/2007-January/001006.html FIC Neo1973] announced in the fall of 2006.<br />
<br />
iPhone UI Demo on youtube http://youtube.com/watch?v=YgW7or1TuFk<br />
<br />
<br />
{| border="1"<br />
!Feature<br />
!iPhone<br />
!Neo1973([[Neo1973#.22Phase_2.22_.28GTA02.2C_.22Mass_Market.22.29|GTA02]]). For the earlier version see [[IPhone_(GTA01)]]<br />
|-<br />
|Announced<br />
|2007-01-09<br />
|2006-11-07 and several updates later<br />
|-<br />
|Dimensions<br />[http://www.sizeasy.com/page/comp/153 visual comparison]<br />
|115 x 61 x 11.6 mm<br />
|120.7 x 62 x 18.5 mm<br />
|-<br />
|Weight<br />
|135 g<br />
|184 g<br />
|-<br />
|Screen<br />
|3.5" 320x480 at 160 ppi, multi-touch<br />
|2.8" 480x640 at 285 ppi, [http://lists.openmoko.org/pipermail/community/2006-December/000576.html maybe multi-touch later]<br />
|-<br />
|Storage<br />
|4 (discontinued, available while supplies last) or 8 GiByte (Not expandable, no memory card slot)<br />
|[http://lists.openmoko.org/pipermail/announce/2007-June/000013.html 256MiByte]<br />
Unconfirmed expandable with [http://www.techtree.com/India/News/Samsung_Readies_8GB_microSD_Card/551-81172-581.html 8GiByte microSD]<br />
|-<br />
|CPU<br />
|[http://www.arm.com/products/CPUs/ARM1176.html ARM1176JZF-S™] (with coprocessor) (Source: [http://www.bitsundso.de/ Bits und so Podcast] [http://www.bitsundso.de/bus20/54/ #20], 8'40" to 9'30" [german language])<br />
|[http://lists.openmoko.org/pipermail/announce/2007-June/000013.html Samsung 2442 @ 400 MHz SoC]<br />
|-<br />
|3D Acceleration<br />
|PowerVR MBX<br />
|SMedia 3362 Graphics Accelerator<br />
|-<br />
|RAM<br />
|<br />
|128MB<br />
|-<br />
|Wireless<br />
|Quad-band GSM, WiFi (b/g), EDGE, Bluetooth 2.0 EDR<br />
|Quad-band GSM, GPRS Class12/CS4/[http://lists.openmoko.org/pipermail/community/2007-September/010400.html b] 2.5G (Not EDGE), [[Neo1973#.22Phase_2.22_.28GTA02.2C_.22Mass_Market.22.29|WiFi]], Bluetooth 2.0 EDR<br />
|-<br />
|Wireless Carrier<br />
|Locked to Apple-selected carrier (AT&T in the US), Can be unlocked (via third-party software)<br />
|Unlocked - any GSM provider<br />
|-<br />
|Embedded devices<br />
|2 megapixel camera, 4 buttons (power, volume up, volume down, mute, Home), [http://en.wikipedia.org/wiki/Accelerometer accelerometer], ambient light sensor, proximity sensor<br />
|GPS, 2 illuminated buttons and [http://lists.openmoko.org/pipermail/announce/2007-June/000013.html 2 3D Accelerometers] [http://lists.openmoko.org/pipermail/community/2007-July/008458.html]<br />
|-<br />
|Operating system<br />
|OS X ([http://www.macworld.co.uk/ipod-itunes/news/index.cfm?newsid=16927 its own version of OS X])<br />
|[[OpenMoko]] Linux (Source code available)<br />
|-<br />
|Software<br />
|Basic PDA + PMP software included. Software can only be created by authorized companies ([http://apple.slashdot.org/article.pl?sid=07/01/12/0430200&from=rss Source])<br />
|Basic PDA included. Software can be created by normal users.<br />
|-<br />
|Video<br />
|Playback; No recording<br />
|No recording. Maybe playback<br />
|-<br />
|Audio<br />
|Playback and recording, speaker; 3.5mm jack (3 conductors: left/right/input)<br />
|Playback and recording, including playback of audio files via GSM and recording/playback of voice calls. 1 watt mono speaker. [ http://lists.openmoko.org/pipermail/community/2007-July/008458.html]<br />
, 2.5 mm jack<br />
|-<br />
|Connectors<br />
|USB 2.0 on proprietary iPod dock connector<br />
|Standard USB 1.1 (unpowered), with a Mini-B receptor (can be connected via adapter to both host and client devices), [[Neo1973_Hardware#Changes_from_GTA01Bv3|exposed I2C, SPI and debug board connector]] inside case in all versions and Debug Board v2 (JTAG and serial console) in Advanced version<br />
|-<br />
|Opening case<br />
|[http://www.anandtech.com/printarticle.aspx?i=3026 voids warranty]<br />
|[http://lists.openmoko.org/pipermail/announce/2007-June/000013.html Advanced version] comes with guitar pick and Torx T6 screwdriver so you can [[Disassembling Neo1973|open case]].<br />
|-<br />
|Battery<br />
|Up to 8 hours talk, up to 7 video, up to 6 online, up to 24 hours audio playback, up to 250 hours standby. Non-user-replaceable Lithium-ion battery, charged via dock connector (USB)<br />
|replaceable 1.7 Ah battery charged via USB<br />
|-<br />
|Ready for use<br />
|Yes<br />
|Yes<br />
|-<br />
|Ready for sale<br />
|US: June 29, 2007, EU: 2007Q4, Asia: 2008<br />
|Retail launch: 20 December 2007<br />
|-<br />
|Price<br />
|USD 299 for 4GiB version (while supplies last), 399 for 8GiB (2 year contract required for activation of either)<br />
|[[Neo1973#.22Phase_2.22_.28GTA02.2C_.22Mass_Market.22.29| USD 450 for Neo Base, USD 600 for Neo Advanced (includes additional development hardware)]]<br />
|-<br />
|Community<br />
|[http://www.google.com/search?client=safari&rls=en&q=iPhone+Community&ie=UTF-8&oe=UTF-8 Google for iPhone Community] to list a few, ##iphone on freenode.net also<br />
|IRC: #openmoko on freenode.net [http://lists.openmoko.org/pipermail/community/ Discussion list], [[Main_Page|Wiki]], [http://lists.openmoko.org/mailman/listinfo/announce Be informed when it is sold]<br />
|-<br />
|Workshops<br />
|[http://www.apple.com/retail/workshops/ Free Hands-on Workshops]<br />
|Set up an OpenMoko event in your area!<br />
|}<br />
{{Languages|iPhone}}<br />
<br />
[[Category:Information]]</div>Bashttp://openmoko.org/wiki/WiFi_support_in_OpenMokoWiFi support in OpenMoko2007-10-06T08:59:54Z<p>Bas: /* AR6k */</p>
<hr />
<div>WiFi support for OpenMoko is in the works. Current [[Neo1973]] GTA01 does not include a wireless LAN chip, but the upcoming [[Neo1973]] GTA02 is going to have one: Atheros AR6K 802.11 b/g.<br />
<br />
== OpenMoko and WiFi ==<br />
<br />
The OpenMoko project would love to add WiFi support to any of the devices on the roadmap.<br />
<br />
<strike>However, we simply are unable to locate a supplier with a suitable product!</strike><br />
<br />
It seems like the choice has been made and Atheros it will be:<br />
From http://lists.openmoko.org/pipermail/community/2007-April/004926.html<br />
<pre>Thanks for being the first to<br />
tell us about Atheros. We're almost for sure going to use their AR6K<br />
chipset in our next product.</pre><br />
<br />
== Public call for WiFi ==<br />
<br />
From [http://lists.openmoko.org/pipermail/community/2007-March/004195.html this mailinglist posting]:<br />
<pre><br />
We can't find a WiFi Chipset with GPL'ed drivers -- We know <br />
this has been discussed (to death) on this list, but as we're <br />
beginning work on the next summer hardware refresh we still can't seem<br />
to find a vendor that meets our strict requirements: Namely, we refuse<br />
to put anything binary in the kernel. <br />
<br />
Marvell has some nice for larger devices (the 8388). But we need<br />
one specifically for mobile phones (like the 8686). If somebody <br />
can help us find the right vendor, we'll give you a free Neo1973. <br />
<br />
If you're a vendor and want to work with us to GPL your driver, we'll <br />
give you lots of business -- and a free phone ;-)<br />
</pre><br />
<br />
=== Regular chipsets are NOT suitable ===<br />
<br />
Please notice that it is '''impossible''' for us to use any of the standard '''desktop''' WiFi chipsets, commonly found in miniPCI cards or USB WiFi adapters.<br />
<br />
We really need a chipset (and even beyond that: Somebody manufacturing SMT modules with that chipset) that is specifically targetted for mobile phones or other mobile devices such as portable media players.<br />
<br />
Regular WiFi chipsets just draw way too much power and are too large by an order of magnitude.<br />
<br />
== List of available WiFi modules for mobile phone usage ==<br />
===SyChip Products===<br />
*WLAN6100EB &mdash; IEEE 802.11g/b Chip Scale Module <br />
*WLAN6064EB &mdash; IEEE 802.11b Embedded Module - Uses Marvell chipset - 88W8381PN, Used in Palm TX (fw 4.102.p0-122 from 2005/08/30, size 82876 bytes, fw stored in 8381Fw.pdb), PN means it uses RF8015 RF chip, while P-only stands for RF8010.<br />
*WLAN6061EB &mdash; IEEE 802.11b Embedded Module - Uses Marvell chipset - 88W8305, Used in Palm LifeDrive (fw 3.0.71p3 from 2005/06/10, size 60420 bytes, fw stored in 8305Fw.pdb)<br />
*Samsung SWL-2450 &mdash; IEEE 802.11b Embedded Module - Uses Marvell chipset - 88W8305, Used in Acer n50<br />
<strike>According to some unofficial sources they use the Prism 3 chipset</strike>. SyChip states they support Linux (but that's all ;-)). Refer to Marvell section further on.<br />
<br />
NOTE: The [http://www.handhelds.org/moin/moin.cgi/PalmLifeDriveHardware?action=highlight&value=lifedrive Palm LifeDrive] uses the SyChip 6061 chipset. several people have extracted the firmware that is being loaded from the driver into the 6061 chip. all indications are that the 6061 is actually using the firmware for the Marvell Libertas 88w8305 chipset. additionally, looking at some firmware for the 6100 series, seems to conclude that it is using the firmware for the Marvell Libertas 88w8385 chipset.<br />
<br />
===Conexant Products===<br />
*CX53121 &mdash; Single-Chip 802.11a/b/g with SPI Interface.<br />
<br />
In this [http://www.linuxdevices.com/news/NS8909671767.html article], they say Conexant Systems supports Linux.<br />
<br />
[http://www.conexant.com/products/entry.jsp?id=408 CX53121] was released on June 2006 and, since it is a 68 square millimeter single chip [http://www.conexant.com/news/news_files/06052006-1.pdf solution], it's a good thing for a mobile device.<br />
<br />
===Broadcom Products===<br />
BCM4326 is a low power device that is said to be linux friendly as per [http://www.broadcom.com/collateral/pb/4326-PB02-R.pdf this document]<br />
<br />
Also, the bcm43xx project could provide a Free driver if Broadcom isn't willing.<br />
<br />
===TI Products===<br />
*WiLink 6.0 (WL1271/WL1273) &mdash; mWLAN / Bluetooth / FM transmit and receive Chip solution [http://www.ti.com/wilink_6 WiLink 6.0]<br />
*WiLink 5.0 (WL1251/WL1253) &mdash; mWLAN / Bluetooth / FM receive Module solution [http://www.ti.com/wilink_5 WiLink 5.0]<br />
*WiLink 4.0 (WL1251/WL1253) &mdash; mWLAN Single-Chip Solution [http://www.ti.com/wilink_4 WiLink 4.0]<br />
<br />
The Product literature claims to be Linux compatible<br />
<br />
ACX 100 has reverse-engineered GPL drivers, and has done for several years. it is a wifi 802.11 chipset from TI that has been used for several years in the HTC smartphone products, including the HTC-designed iPAQs (HTC designs all of Compaq/HP's iPAQs)<br />
<br />
I assume that you are happy to have binary-only firmware uploaded to turn chips into actual useful products.<br />
<br />
===NXP Products===<br />
* [http://www.nxp.com/acrobat_download/literature/9397/75015597.pdf BGW200 Low-power WLAN 802.11b SiP]<br />
* [http://www.nxp.com/acrobat_download/literature/9397/75015598.pdf BGW211 Low-power WLAN 802.11g SiP]<br />
<br />
Linux drivers are available and in production use but not GPL'd yet. <br />
<br />
New product touted as Linux friendly:<br />
* [http://linuxdevices.com/news/NS2781864762.html BGM220 "world smallest WLAN SoC"]<br />
Note: The product won't ship in Volume until Q4 which means it's probably not very useful right now.<br />
The Product literature mentions reference design software support for Linux operating system.<br />
<br />
===Key Stream Corporation===<br />
Based in Japan. Linux support unknown. Has a few "low power" chips. Most useful info in Japanese. English site:<br />
http://www.keystream.co.jp/en/<br />
<br />
===ZyDAS ZD1211 chipset===<br />
ZyDAS ZD1211 is a chipset designed to work with small power consumption. It fits the power supply from USB and is used by many USB wifi adapters. Interestingly, it supports "access point mode" which allows other adapters to connect to.<br />
<br />
'''Chipset specifications:'''<br />
* 802.11a/b/g support (few sticks support 802.11a though)<br />
* USB 2.0 support (802.11b only on USB 1.1)<br />
* typical current consumption: 150mA (idle), 200mA (sending)<br />
* WEP64/128/256, WPA-PSK<br />
* Station and Ad hoc mode <br />
<br />
The source code of the driver was initially contributed by ZyDAS under the GPL license, the ZD1211 Linux driver is maintained by the open source community.<br />
<br />
Comunity site of the driver: [http://zd1211.ath.cx/ http://zd1211.ath.cx/] It has been included in the kernel since version 2.6.18.<br />
<br />
===Mstar===<br />
<br />
According to a friend, Mstar semiconductor has a new low power wifi chip, no info about Linux though.<br />
<br />
[http://mstarsemi.com.tw/ Mstar Semiconductor] email: contact_us at mstarsemi.com.tw<br />
<br />
<br />
===Accton===<br />
<br />
* Accton WM3236AB provides Atheros AR6001 b/g with 11x11mm size<br />
<br />
* Accton WM3236AQ provides Atheros AR6001 b/g with 13x13mm size<br />
<br />
== List of chipset vendors who are known to be at least partially GPL friendly ==<br />
<br />
=== Marvell ===<br />
[http://wiki.laptop.org/go/Libertas Libertas] (includes the 88W8305, 88W8381, 88W8385, 88W8388 and 88W8686)<br />
<br />
According to prplague on #openmoko, [http://www.zcomax.com/1mbfile/G%20product/XG-880M_specification%20.pdf Zcomax XG-880M module] might fit the requirements.<br />
<br />
[http://www.embeddedworks.net/newsite/WLAN/oem_SMD_80211g.html Embedded Works] provides SMD versions of 88w8385 which are 9.6x9.6x1.7 mm big.<br />
This chip should be quite more power-consuming than other products on the market.<br />
<br />
Status:<br><br />
*USB 88W8388 - fully supported by GPL libertas driver<br><br />
*CF 88W8385 - driver based on GPL libertas driver by Holger Schurig (libertas_cs)<br><br />
*CF 88W8305 - driver is work in progress, firmware can be loaded and basic communication with firmware works (based on 8385 driver)<br><br />
*CF 88W8381 - driver is work in progress, nothing done yet<br><br />
*SD 88W8686 - driver by Marvell, available here [http://marvell.com/drivers/driverDisplay.do?dId=178&pId=38 <br />
<br />
*http://marvell.com/drivers/driverDisplay.do?dId=178&pId=38]<br />
<br />
As for the driver git tree, see here (GPL, in sync with mainline, supporting USB8388 and partly CF8385):<br />
[http://git.infradead.org/?p=libertas-2.6.git;a=summary http://git.infradead.org/?p=libertas-2.6.git;a=summary]<br><br />
For CF8385 patches, see [http://projects.linuxtogo.org/scm/?group_id=24 http://projects.linuxtogo.org/scm/?group_id=24]<br />
<br />
Marvell also cooperates with Gumstix(TM) and released this driver (GPL, supporting 2.6.15.1, supporting CF8385):<br />
[http://files.gumstix.com/cf8385-5.0.16.p0-26306.tbz http://files.gumstix.com/cf8385-5.0.16.p0-26306.tbz]<br />
<br />
=== Zydas ===<br />
[http://zd1211.ath.cx/ Homepage]<br />
<br />
=== Ralink ===<br />
[http://www.ralinktech.com/ralink/Home.html Homepage]<br />
<br />
The new [http://www.ralinktech.com/ralink/data/RT2501_Brochure.pdf RT2501] Wireless Chipset from Ralink seems to have been released with GPL [http://www.ralinktech.com/ralink/Home/Support/Linux.html drivers]. Ralink <i>is very active in the Linux community, and provides source code for many of its client drivers to developers.</i> Moreover esists an rt2x00 Open Source [http://sourceforge.net/projects/rt2400/ Project] on Sourceforge aiming to create <i>a stable and feature rich Linux driver for wireless 802.11b and 802.11g cards that are based on the Ralink rt2400 and rt2500 chipsets.</i><br />
This chipset has many interesting features as: <u>Bluetooth Co-existence</u>, <u>Low Power with Advanced Power Management</u>, <u>Linux AP Driver.</u><br />
<br />
=== Atheros ===<br />
==== AR6k ====<br />
The AR6K has a GPL host driver available today. The firmware that runs on the AR6K is quite closed, but that's the case with most, if not any of these radios. No binary modules would need to be run in the kernel. A company called Card Access Inc. sells dev boards and kits and provides commercial support for the AR6K. Modules with the AR6K are available from Card Access Inc.<br />
<br />
and also provide by accton@taiwan in size 11.4 X 10.85 X 1.75 802.11 b/g,power consumption and BT coexistance function: http://www.accton.com/products/product_range/21_weap/WM3236A.AQ.htm<br />
<br />
This sounds like a really great device since it supports WEP, WPA and WPA2<br />
* http://atheros.com/pt/bulletins/AR6001GLBulletin.pdf<br />
* http://atheros.com/pt/bulletins/AR6001XLBulletin.pdf<br />
* http://sourceforge.net/project/showfiles.php?group_id=186068<br />
<br />
=== Nanoradio ===<br />
These guys have a mobile WiFi solution;<br />
* http://www.nanoradio.com/?NavID=273<br />
<br />
and they do state that they support Linux;<br />
* http://www.nanoradio.com/?NavID=293<br />
<br />
However, they don't say whether it is GPL'd but it might be worth checking out.<br />
<br />
=== STMicroelectronics ===<br />
STMicroelectronics, headquartered in Switzerland, also has a radio on chip solution it says on:<br />
<br />
* http://linuxdevices.com/news/NS7045943711.html<br />
* http://www.st.com/stonline/products/families/communication/wscomm/wlan/wlan.htm<br />
<br />
Three chipsets that may work, STLC4550(single band b/g), STLC4420(dual band a/b/g) and STLC4370(single band b/g). Press release state "ST offers manufacturers a complete WLAN hardware and software solution, with source code in house"..."operating systems including" ..."Linux"<br />
http://www.st.com/stonline/stappl/press/news/year2006/p2020.htm<br />
<br />
Interesting to add to the other options: The STLC4420 seems to be priced at $9 a per unit on buying 100k units.<br />
<br />
It seems that STLC4550 is a derivative of Conexant CX3110x as dmesg from Nokia Maemo devices show the following:<br />
<4>[ 5.223236] CX3110x chip variant: STLC4550 <br />
<4>[ 5.305053] CX3110x: firmware version: 2.13.0.0.a.22.1 <br />
<4>[ 5.320709] Loaded CX3110x driver, version 0.8 "<br />
whereas CX3110x is a Conexant's 802.11 b/g embedded chipset for which they have a driver at https://garage.maemo.org/projects/cx3110x/ which supposedly is GPL. <br />
<br />
However: Just above the dmesg output cited above there's the following line <br />
<4>[ 5.064849] umac: module license 'Proprietary' taints kernel. <br />
and umac likely is needed for cx3110x to work.<br />
<br />
=== Conexant ===<br />
related to entry above is http://www.conexant.com/products/entry.jsp?id=375 (CX53111)<br />
<br />
An inquiry on #maemo yields bad news:<br />
<buz> i'm wondering about the cx3110c driver<br />
<buz> is that fully opensource now?or does it still need proprietary modules?<br />
<neal> the latter<br />
<br />
But see http://maemo.org/pipermail/maemo-developers/2006-April/003575.html and http://prism54.org/freemac.html for reverse engineered GPL drivers for some Conexant cards.<br />
<br />
=== CSR ===<br />
<br />
[http://www.csr.com/home.php CSR] released an innovative single-chip solution for WiFI called UniFi(tm). The new [http://www.csr.com/products/unifiport2abg_over.htm UniFi-2] Portable is a <b>Dual RISC microcontrollers based</b> solution really really small and powerful. The company gives support to Linux and Windows developers with a dedicated [http://www.csrsupport.com/ website] and an SDK package. The same company has launched UniVox, a VoIP phone based on this UniFi single-chip Wi-Fi technology.<br />
Driver is available for Linux, but not as GPL.<br />
<br />
=== AW-GH320 ===<br />
<br />
http://www.streamunlimited.com/about/show/wireless%20modules<br />
<br />
The module IC is targeted to mobile devices including Mobile Phones, Digital Still Cameras (DSCs), Portable Media Players (PMPs), Personal Digital Assistants (PDAs), and Gaming Devices which need small footprint package, low power consumption, multiple interfaces and OS support.<br />
<br />
Contact robin.slond@streamunlimited.com as streamunlimited is doing a lot of embedded Linux development.<br />
<br />
[[Category:Neo1973_Phase_1_related]]</div>Bashttp://openmoko.org/wiki/WiFi_support_in_OpenMokoWiFi support in OpenMoko2007-10-06T08:56:53Z<p>Bas: /* Nanoradio */</p>
<hr />
<div>WiFi support for OpenMoko is in the works. Current [[Neo1973]] GTA01 does not include a wireless LAN chip, but the upcoming [[Neo1973]] GTA02 is going to have one: Atheros AR6K 802.11 b/g.<br />
<br />
== OpenMoko and WiFi ==<br />
<br />
The OpenMoko project would love to add WiFi support to any of the devices on the roadmap.<br />
<br />
<strike>However, we simply are unable to locate a supplier with a suitable product!</strike><br />
<br />
It seems like the choice has been made and Atheros it will be:<br />
From http://lists.openmoko.org/pipermail/community/2007-April/004926.html<br />
<pre>Thanks for being the first to<br />
tell us about Atheros. We're almost for sure going to use their AR6K<br />
chipset in our next product.</pre><br />
<br />
== Public call for WiFi ==<br />
<br />
From [http://lists.openmoko.org/pipermail/community/2007-March/004195.html this mailinglist posting]:<br />
<pre><br />
We can't find a WiFi Chipset with GPL'ed drivers -- We know <br />
this has been discussed (to death) on this list, but as we're <br />
beginning work on the next summer hardware refresh we still can't seem<br />
to find a vendor that meets our strict requirements: Namely, we refuse<br />
to put anything binary in the kernel. <br />
<br />
Marvell has some nice for larger devices (the 8388). But we need<br />
one specifically for mobile phones (like the 8686). If somebody <br />
can help us find the right vendor, we'll give you a free Neo1973. <br />
<br />
If you're a vendor and want to work with us to GPL your driver, we'll <br />
give you lots of business -- and a free phone ;-)<br />
</pre><br />
<br />
=== Regular chipsets are NOT suitable ===<br />
<br />
Please notice that it is '''impossible''' for us to use any of the standard '''desktop''' WiFi chipsets, commonly found in miniPCI cards or USB WiFi adapters.<br />
<br />
We really need a chipset (and even beyond that: Somebody manufacturing SMT modules with that chipset) that is specifically targetted for mobile phones or other mobile devices such as portable media players.<br />
<br />
Regular WiFi chipsets just draw way too much power and are too large by an order of magnitude.<br />
<br />
== List of available WiFi modules for mobile phone usage ==<br />
===SyChip Products===<br />
*WLAN6100EB &mdash; IEEE 802.11g/b Chip Scale Module <br />
*WLAN6064EB &mdash; IEEE 802.11b Embedded Module - Uses Marvell chipset - 88W8381PN, Used in Palm TX (fw 4.102.p0-122 from 2005/08/30, size 82876 bytes, fw stored in 8381Fw.pdb), PN means it uses RF8015 RF chip, while P-only stands for RF8010.<br />
*WLAN6061EB &mdash; IEEE 802.11b Embedded Module - Uses Marvell chipset - 88W8305, Used in Palm LifeDrive (fw 3.0.71p3 from 2005/06/10, size 60420 bytes, fw stored in 8305Fw.pdb)<br />
*Samsung SWL-2450 &mdash; IEEE 802.11b Embedded Module - Uses Marvell chipset - 88W8305, Used in Acer n50<br />
<strike>According to some unofficial sources they use the Prism 3 chipset</strike>. SyChip states they support Linux (but that's all ;-)). Refer to Marvell section further on.<br />
<br />
NOTE: The [http://www.handhelds.org/moin/moin.cgi/PalmLifeDriveHardware?action=highlight&value=lifedrive Palm LifeDrive] uses the SyChip 6061 chipset. several people have extracted the firmware that is being loaded from the driver into the 6061 chip. all indications are that the 6061 is actually using the firmware for the Marvell Libertas 88w8305 chipset. additionally, looking at some firmware for the 6100 series, seems to conclude that it is using the firmware for the Marvell Libertas 88w8385 chipset.<br />
<br />
===Conexant Products===<br />
*CX53121 &mdash; Single-Chip 802.11a/b/g with SPI Interface.<br />
<br />
In this [http://www.linuxdevices.com/news/NS8909671767.html article], they say Conexant Systems supports Linux.<br />
<br />
[http://www.conexant.com/products/entry.jsp?id=408 CX53121] was released on June 2006 and, since it is a 68 square millimeter single chip [http://www.conexant.com/news/news_files/06052006-1.pdf solution], it's a good thing for a mobile device.<br />
<br />
===Broadcom Products===<br />
BCM4326 is a low power device that is said to be linux friendly as per [http://www.broadcom.com/collateral/pb/4326-PB02-R.pdf this document]<br />
<br />
Also, the bcm43xx project could provide a Free driver if Broadcom isn't willing.<br />
<br />
===TI Products===<br />
*WiLink 6.0 (WL1271/WL1273) &mdash; mWLAN / Bluetooth / FM transmit and receive Chip solution [http://www.ti.com/wilink_6 WiLink 6.0]<br />
*WiLink 5.0 (WL1251/WL1253) &mdash; mWLAN / Bluetooth / FM receive Module solution [http://www.ti.com/wilink_5 WiLink 5.0]<br />
*WiLink 4.0 (WL1251/WL1253) &mdash; mWLAN Single-Chip Solution [http://www.ti.com/wilink_4 WiLink 4.0]<br />
<br />
The Product literature claims to be Linux compatible<br />
<br />
ACX 100 has reverse-engineered GPL drivers, and has done for several years. it is a wifi 802.11 chipset from TI that has been used for several years in the HTC smartphone products, including the HTC-designed iPAQs (HTC designs all of Compaq/HP's iPAQs)<br />
<br />
I assume that you are happy to have binary-only firmware uploaded to turn chips into actual useful products.<br />
<br />
===NXP Products===<br />
* [http://www.nxp.com/acrobat_download/literature/9397/75015597.pdf BGW200 Low-power WLAN 802.11b SiP]<br />
* [http://www.nxp.com/acrobat_download/literature/9397/75015598.pdf BGW211 Low-power WLAN 802.11g SiP]<br />
<br />
Linux drivers are available and in production use but not GPL'd yet. <br />
<br />
New product touted as Linux friendly:<br />
* [http://linuxdevices.com/news/NS2781864762.html BGM220 "world smallest WLAN SoC"]<br />
Note: The product won't ship in Volume until Q4 which means it's probably not very useful right now.<br />
The Product literature mentions reference design software support for Linux operating system.<br />
<br />
===Key Stream Corporation===<br />
Based in Japan. Linux support unknown. Has a few "low power" chips. Most useful info in Japanese. English site:<br />
http://www.keystream.co.jp/en/<br />
<br />
===ZyDAS ZD1211 chipset===<br />
ZyDAS ZD1211 is a chipset designed to work with small power consumption. It fits the power supply from USB and is used by many USB wifi adapters. Interestingly, it supports "access point mode" which allows other adapters to connect to.<br />
<br />
'''Chipset specifications:'''<br />
* 802.11a/b/g support (few sticks support 802.11a though)<br />
* USB 2.0 support (802.11b only on USB 1.1)<br />
* typical current consumption: 150mA (idle), 200mA (sending)<br />
* WEP64/128/256, WPA-PSK<br />
* Station and Ad hoc mode <br />
<br />
The source code of the driver was initially contributed by ZyDAS under the GPL license, the ZD1211 Linux driver is maintained by the open source community.<br />
<br />
Comunity site of the driver: [http://zd1211.ath.cx/ http://zd1211.ath.cx/] It has been included in the kernel since version 2.6.18.<br />
<br />
===Mstar===<br />
<br />
According to a friend, Mstar semiconductor has a new low power wifi chip, no info about Linux though.<br />
<br />
[http://mstarsemi.com.tw/ Mstar Semiconductor] email: contact_us at mstarsemi.com.tw<br />
<br />
<br />
===Accton===<br />
<br />
* Accton WM3236AB provides Atheros AR6001 b/g with 11x11mm size<br />
<br />
* Accton WM3236AQ provides Atheros AR6001 b/g with 13x13mm size<br />
<br />
== List of chipset vendors who are known to be at least partially GPL friendly ==<br />
<br />
=== Marvell ===<br />
[http://wiki.laptop.org/go/Libertas Libertas] (includes the 88W8305, 88W8381, 88W8385, 88W8388 and 88W8686)<br />
<br />
According to prplague on #openmoko, [http://www.zcomax.com/1mbfile/G%20product/XG-880M_specification%20.pdf Zcomax XG-880M module] might fit the requirements.<br />
<br />
[http://www.embeddedworks.net/newsite/WLAN/oem_SMD_80211g.html Embedded Works] provides SMD versions of 88w8385 which are 9.6x9.6x1.7 mm big.<br />
This chip should be quite more power-consuming than other products on the market.<br />
<br />
Status:<br><br />
*USB 88W8388 - fully supported by GPL libertas driver<br><br />
*CF 88W8385 - driver based on GPL libertas driver by Holger Schurig (libertas_cs)<br><br />
*CF 88W8305 - driver is work in progress, firmware can be loaded and basic communication with firmware works (based on 8385 driver)<br><br />
*CF 88W8381 - driver is work in progress, nothing done yet<br><br />
*SD 88W8686 - driver by Marvell, available here [http://marvell.com/drivers/driverDisplay.do?dId=178&pId=38 <br />
<br />
*http://marvell.com/drivers/driverDisplay.do?dId=178&pId=38]<br />
<br />
As for the driver git tree, see here (GPL, in sync with mainline, supporting USB8388 and partly CF8385):<br />
[http://git.infradead.org/?p=libertas-2.6.git;a=summary http://git.infradead.org/?p=libertas-2.6.git;a=summary]<br><br />
For CF8385 patches, see [http://projects.linuxtogo.org/scm/?group_id=24 http://projects.linuxtogo.org/scm/?group_id=24]<br />
<br />
Marvell also cooperates with Gumstix(TM) and released this driver (GPL, supporting 2.6.15.1, supporting CF8385):<br />
[http://files.gumstix.com/cf8385-5.0.16.p0-26306.tbz http://files.gumstix.com/cf8385-5.0.16.p0-26306.tbz]<br />
<br />
=== Zydas ===<br />
[http://zd1211.ath.cx/ Homepage]<br />
<br />
=== Ralink ===<br />
[http://www.ralinktech.com/ralink/Home.html Homepage]<br />
<br />
The new [http://www.ralinktech.com/ralink/data/RT2501_Brochure.pdf RT2501] Wireless Chipset from Ralink seems to have been released with GPL [http://www.ralinktech.com/ralink/Home/Support/Linux.html drivers]. Ralink <i>is very active in the Linux community, and provides source code for many of its client drivers to developers.</i> Moreover esists an rt2x00 Open Source [http://sourceforge.net/projects/rt2400/ Project] on Sourceforge aiming to create <i>a stable and feature rich Linux driver for wireless 802.11b and 802.11g cards that are based on the Ralink rt2400 and rt2500 chipsets.</i><br />
This chipset has many interesting features as: <u>Bluetooth Co-existence</u>, <u>Low Power with Advanced Power Management</u>, <u>Linux AP Driver.</u><br />
<br />
=== Atheros ===<br />
==== AR6k ====<br />
The AR6K has a GPL host driver available today. The firmware that runs on the AR6K is quite closed, but that's the case with most, if not any of these radios. No binary modules would need to be run in the kernel. A company called Card Access Inc. sells dev boards and kits and provides commercial support for the AR6K. Modules with the AR6K are available from Card Access Inc.<br />
<br />
and also provide by accton@taiwan in size 11.4 X 10.85 X 1.75 802.11 b/g,power consumption and BT coexistance function: http://www.accton.com/products/product_range/21_weap/WM3236A.AQ.htm<br />
<br />
This sounds like a really great device<br />
* http://atheros.com/pt/bulletins/AR6001GLBulletin.pdf<br />
* http://atheros.com/pt/bulletins/AR6001XLBulletin.pdf<br />
* http://sourceforge.net/project/showfiles.php?group_id=186068<br />
<br />
=== Nanoradio ===<br />
These guys have a mobile WiFi solution;<br />
* http://www.nanoradio.com/?NavID=273<br />
<br />
and they do state that they support Linux;<br />
* http://www.nanoradio.com/?NavID=293<br />
<br />
However, they don't say whether it is GPL'd but it might be worth checking out.<br />
<br />
=== STMicroelectronics ===<br />
STMicroelectronics, headquartered in Switzerland, also has a radio on chip solution it says on:<br />
<br />
* http://linuxdevices.com/news/NS7045943711.html<br />
* http://www.st.com/stonline/products/families/communication/wscomm/wlan/wlan.htm<br />
<br />
Three chipsets that may work, STLC4550(single band b/g), STLC4420(dual band a/b/g) and STLC4370(single band b/g). Press release state "ST offers manufacturers a complete WLAN hardware and software solution, with source code in house"..."operating systems including" ..."Linux"<br />
http://www.st.com/stonline/stappl/press/news/year2006/p2020.htm<br />
<br />
Interesting to add to the other options: The STLC4420 seems to be priced at $9 a per unit on buying 100k units.<br />
<br />
It seems that STLC4550 is a derivative of Conexant CX3110x as dmesg from Nokia Maemo devices show the following:<br />
<4>[ 5.223236] CX3110x chip variant: STLC4550 <br />
<4>[ 5.305053] CX3110x: firmware version: 2.13.0.0.a.22.1 <br />
<4>[ 5.320709] Loaded CX3110x driver, version 0.8 "<br />
whereas CX3110x is a Conexant's 802.11 b/g embedded chipset for which they have a driver at https://garage.maemo.org/projects/cx3110x/ which supposedly is GPL. <br />
<br />
However: Just above the dmesg output cited above there's the following line <br />
<4>[ 5.064849] umac: module license 'Proprietary' taints kernel. <br />
and umac likely is needed for cx3110x to work.<br />
<br />
=== Conexant ===<br />
related to entry above is http://www.conexant.com/products/entry.jsp?id=375 (CX53111)<br />
<br />
An inquiry on #maemo yields bad news:<br />
<buz> i'm wondering about the cx3110c driver<br />
<buz> is that fully opensource now?or does it still need proprietary modules?<br />
<neal> the latter<br />
<br />
But see http://maemo.org/pipermail/maemo-developers/2006-April/003575.html and http://prism54.org/freemac.html for reverse engineered GPL drivers for some Conexant cards.<br />
<br />
=== CSR ===<br />
<br />
[http://www.csr.com/home.php CSR] released an innovative single-chip solution for WiFI called UniFi(tm). The new [http://www.csr.com/products/unifiport2abg_over.htm UniFi-2] Portable is a <b>Dual RISC microcontrollers based</b> solution really really small and powerful. The company gives support to Linux and Windows developers with a dedicated [http://www.csrsupport.com/ website] and an SDK package. The same company has launched UniVox, a VoIP phone based on this UniFi single-chip Wi-Fi technology.<br />
Driver is available for Linux, but not as GPL.<br />
<br />
=== AW-GH320 ===<br />
<br />
http://www.streamunlimited.com/about/show/wireless%20modules<br />
<br />
The module IC is targeted to mobile devices including Mobile Phones, Digital Still Cameras (DSCs), Portable Media Players (PMPs), Personal Digital Assistants (PDAs), and Gaming Devices which need small footprint package, low power consumption, multiple interfaces and OS support.<br />
<br />
Contact robin.slond@streamunlimited.com as streamunlimited is doing a lot of embedded Linux development.<br />
<br />
[[Category:Neo1973_Phase_1_related]]</div>Bas