http://openmoko.org/api.php?action=feedcontributions&user=Mike&feedformat=atomOpenmoko - User contributions [en]2024-03-28T15:57:12ZUser contributionsMediaWiki 1.19.24http://openmoko.org/wiki/Openmoko_Local_Groups:_DenverOpenmoko Local Groups: Denver2007-08-23T18:37:39Z<p>Mike: </p>
<hr />
<div>Are there any other OpenMoko community members here?<br />
<br />
{|border=1<br />
!Name<br />
!Skills<br />
!Interest<br />
!Location<br />
! Has Device<br />
|-<br />
|[[User:mike|Mike Welter]]<br />
|Programming/Hardware<br />
|Location-based apps.<br />
|Evergreen, CO (Denver)<br />
|Yes (and debug board)<br />
|}<br />
<br />
<br />
[[Category:Community]]</div>Mikehttp://openmoko.org/wiki/Openmoko_Local_Groups:_DenverOpenmoko Local Groups: Denver2007-08-23T18:37:05Z<p>Mike: </p>
<hr />
<div>Are there any other OpenMoko community members here?<br />
<br />
{|border=1<br />
!Name<br />
!Skills<br />
!Interest<br />
!Location<br />
! Has Device<br />
|-<br />
|[[User:mike|Mike Welter]]<br />
|Programming/Hardware<br />
|Location-based apps.<br />
|Evergreen, CO<br />
|Yes (and debug board)<br />
|}<br />
<br />
<br />
[[Category:Community]]</div>Mikehttp://openmoko.org/wiki/Openmoko_Local_Groups:_DenverOpenmoko Local Groups: Denver2007-08-16T21:07:29Z<p>Mike: </p>
<hr />
<div>Are there any other OpenMoko community members here?<br />
<br />
{|border=1<br />
!Name<br />
!Skills<br />
!Interest<br />
!Location<br />
! Has Device<br />
|-<br />
|[[User:mike|Mike Welter]]<br />
|Programming/Hardware<br />
|Location-based apps.<br />
|Evergreen, CO<br />
|Yes<br />
|}<br />
<br />
<br />
[[Category:Community]]</div>Mikehttp://openmoko.org/wiki/Openmoko_Local_GroupsOpenmoko Local Groups2007-08-16T21:03:47Z<p>Mike: </p>
<hr />
<div>__TOC__<br />
'''OpenMoko Local Groups...'''<br />
<br />
* can be used for developers to meet and get to know each other<br />
* can be used for developing<br />
* may provide the room for real-life discussions away from mailinglists/wiki<br />
* can support early support handling their GTA01Bv4 and exchange experiences<br />
* fasten the community's cohesion<br />
* give motivation<br />
<br />
== EU ==<br />
<br />
* Austria<br />
** [[OpenMoko_Local_Groups: Vienna|Vienna]] <br />
<br />
* Belgium<br />
** [[OpenMoko_local_Groups: Antwerp|Antwerp]]<br />
<br />
* Denmark<br />
** [[OpenMoko_local_Groups: Copenhagen|Copenhagen]]<br />
<br />
* Finland <br />
** [[OpenMoko_Local_Groups: Helsinki|Helsinki]] <br />
<br />
* France <br />
** [[OpenMoko_Local_Groups: Paris|Paris]]<br />
** [[OpenMoko_Local_Groups: Toulouse|Toulouse]] <br />
<br />
* Germany <br />
** [[OpenMoko_Local_Groups: Berlin|Berlin]]<br />
** [[OpenMoko_Local_Groups: Braunschweig|Braunschweig]]<br />
** [[OpenMoko_Local_Groups: Duesseldorf|Duesseldorf]] <br />
** [[OpenMoko_Local_Groups: Frankfurt Main|Frankfurt Main]] <br />
** [[OpenMoko_Local_Groups: OWL|OWL]]<br />
** [[OpenMoko_Local_Groups: Ingolstadt|Ingolstadt]]<br />
<br />
* [[OpenMoko_Local_Groups:_Netherlands|Netherlands]] <br />
** [[OpenMoko_Local_Groups: Amsterdam|Amsterdam]] <br />
** [[OpenMoko_Local_Groups: Den Haag|Den Haag/The Hague]] <br />
** [[OpenMoko_Local_Groups: Eindhoven|Eindhoven]] <br />
** [[OpenMoko_Local_Groups: Ede|Ede]]<br />
<br />
* Italy<br />
** [[OpenMoko_Local_Groups: Milan|Milan]] <br />
** [[OpenMoko_Local_Groups: Turin|Turin]] <br />
<br />
* [[OpenMoko_Local_Groups:_Norway|Norway]]<br />
** [[OpenMoko_Local_Groups:_Oslo|Oslo]]<br />
** [[OpenMoko_Local_Groups: Trondheim|Trondheim]] <br />
<br />
* Poland <br />
** [[OpenMoko_Local_Groups: Warsaw|Warsaw]] <br />
<br />
* [[OpenMoko_Local_Groups:_Portugal|Portugal]]<br />
** [[OpenMoko_Local_Groups: Braga|Braga]] <br />
<br />
* Romania<br />
** [[OpenMoko_Local_Groups: Bucharest|Bucharest]]<br />
<br />
* Slovakia<br />
** [[OpenMoko_Local_Groups: Bratislava|Bratislava]]<br />
<br />
* Spain <br />
** [[OpenMoko_Local_Groups: Madrid|Madrid]] <br />
<br />
* Sweden <br />
** [[OpenMoko_Local_Groups: Gothenburg|Gothenburg]] <br />
<br />
* [[OpenMoko_Local_Groups: Switzerland|Switzerland]]<br />
** [[OpenMoko_Local_Groups: Bern|Bern]] <br />
<br />
* UK<br />
** England<br />
*** [[OpenMoko_Local_Groups: Birmingham|Birmingham]] <br />
*** [[OpenMoko_Local_Groups: London|London]]<br />
** Scotland<br />
*** [[OpenMoko_Local_Groups: Fife|Fife]]<br />
*** [[OpenMoko_Local_Groups: Edinburgh|Edinburgh]]<br />
<br />
== Oceania ==<br />
<br />
* Australia <br />
** [[OpenMoko_Local_Groups: Adelaide|Adelaide]]<br />
** [[OpenMoko_Local_Groups: Canberra|Canberra]]<br />
** [[OpenMoko_Local_Groups: Melbourne|Melbourne]]<br />
<br />
* New Zealand<br />
** [[OpenMoko_Local_Groups: Auckland|Auckland]]<br />
** [[OpenMoko_Local_Groups: Christchurch|Christchurch]]<br />
<br />
== Asia ==<br />
* India<br />
** [[OpenMoko_Local_Groups: Delhi|Delhi]]<br />
* Singapore<br />
** [[OpenMoko_Local_Groups: Singapore|Singapore]]<br />
<br />
== USA ==<br />
* Alabama<br />
** [[OpenMoko_Local_Groups: Alabama|Alabama]]<br />
<br />
* Arizona<br />
** [[OpenMoko_Local_Groups: Arizona|Arizona]]<br />
<br />
* California <br />
** [[OpenMoko_Local_Groups: San Diego|San Diego]] <br />
** [[OpenMoko_Local_Groups: San Francisco|San Francisco]] <br />
** [[OpenMoko_Local_Groups: Sacramento|Sacramento]]<br />
<br />
* Colorado<br />
** [[OpenMoko_Local_Groups: Colorado Springs|Colorado Springs]]<br />
** [[OpenMoko_Local_Groups: Denver|Denver]]<br />
<br />
* District of Columbia<br />
** [[OpenMoko_Local_Groups: Washington DC Metro | Washington DC Metro]]<br />
<br />
* Florida<br />
** [[OpenMoko_Local_Groups: Central Florida | Central Florida]]<br />
<br />
* Georgia<br />
** [[OpenMoko_Local_Groups: Atlanta | Atlanta]]<br />
<br />
* Illinois <br />
** [[OpenMoko_Local_Groups: Chicago|Chicago]]<br />
<br />
* Indiana<br />
** [[OpenMoko_Local_Groups: Bloomington|Bloomington]]<br />
<br />
* Iowa<br />
** [[OpenMoko_Local_Groups: Iowa-Ames | Iowa-Ames]] <br />
<br />
* Massachusetts<br />
** [[OpenMoko_Local_groups: Boston|Boston]]<br />
<br />
* Michigan <br />
** [[OpenMoko_Local_Groups: Detroit|Detroit]] <br />
<br />
* New Jersey<br />
** [[OpenMoko_Local_Groups: Stevens Institute of Technology, Hoboken NJ | Stevens Institute of Technology, Hoboken NJ ]]<br />
<br />
* New York<br />
** [[OpenMoko_Local_Groups: NYC Metro | NYC Metro]]<br />
<br />
* North Carolina<br />
** [[OpenMoko Local_Groups: Charlotte | Charlotte]]<br />
<br />
* Ohio <br />
** [[OpenMoko_Local_Groups: Cleveland|Cleveland]] <br />
<br />
* Oregon <br />
** [[OpenMoko_Local_Groups: Eugene|Eugene]] <br />
** [[OpenMoko_Local_Groups: Portland|Portland]] <br />
<br />
* Texas <br />
** [[OpenMoko_Local_Groups: North Texas|North Texas]]<br />
** [[OpenMoko_Local_Groups: Central Texas|Central Texas]]<br />
<br />
* Utah<br />
** [[OpenMoko_Local_Groups: Salt Lake|Salt Lake]]<br />
<br />
* Virginia<br />
** [[OpenMoko_Local_Groups: Virginia|Virginia]]<br />
<br />
== Canada ==<br />
* Alberta<br />
** [[OpenMoko_Local_Groups: Calgary|Calgary]]<br />
** [[OpenMoko_Local_Groups: Edmonton|Edmonton]]<br />
** [[OpenMoko_Local_Groups: Pincher Creek|Pincher Creek]]<br />
* British Columbia<br />
** [[OpenMoko_Local_Groups: Vancouver|Vancouver]]<br />
* Ontario<br />
** [[OpenMoko_Local_Groups: Ottawa|Ottawa]]<br />
** [[OpenMoko_Local_Groups: Toronto|Toronto]]<br />
* Quebec <br />
** [[OpenMoko_Local_Groups: Montreal|Montreal]]<br />
<br />
== Colombia ==<br />
* Bogotá<br />
** [[OpenMoko_Local_Groups: Bogota|Bogotá]]<br />
<br />
<br />
[[Category:Community]]<br />
[[Category:Neo1973 Phase 1 related]]</div>Mikehttp://openmoko.org/wiki/Openmoko_Local_Groups:_DenverOpenmoko Local Groups: Denver2007-08-16T21:03:23Z<p>Mike: </p>
<hr />
<div>Please add your contact info here:<br />
<br />
* Mike Welter (mike@introspect.com)</div>Mikehttp://openmoko.org/wiki/ApplicationsApplications2007-02-18T18:50:56Z<p>Mike: </p>
<hr />
<div>== Overview ==<br />
Although [[OpenMoko]] is designed for smartphones that use a stylus, it would be foolish to expect people to only operate their handsets with stylus. For this reason, some core phone-related applications will be developed with finger (as opposed to stylus navigation) in mind.<br />
<br />
{{note| Applications listed on this page are listing in order of priority and by phase. 0th phase is for the developers preview release in February, 1st phase is for March. 2nd phase is September... when we are ready for mass market appeal.}}<br />
<br />
== General Principles ==<br />
* All modifications are saved instantenously, there should never be a save command.<br />
* Make sure users can't make interface operation errors, or that the effects are easily reversible, instead of just notifying them of the potential consequences of their actions.<br />
* When you open a document you should be returned to the place where you were working when you last closed or save it (this is our concept of sessions).<br />
* Label buttons with adjectives, which describe the state of the object affected<br />
* Designers should seek an efficient monotonous solution to gain benefits, including ease of learning, simplicity of implementation, minimization of documentation, and lowered maintenance costs.<br />
* Whenever you find yourself specifying an error message, please stop; then redesign the interface so that the condition that generated the error message doesn't arise.<br />
* If the user gets no utility from a process, there is no reason to tell them that it is happening.<br />
<br />
{{note|Innovation usually happens at the bottom. What we need to do is provide consistent ways to develop and deploy appliations.}}<br />
<br />
==Finger-Based Applications ==<br />
<br />
=== 0th Phase ===<br />
* [[Dialer]]<br />
* [[Main Menu]]<br />
<br />
=== 1st Phase ===<br />
* [[Music Player]]<br />
* [[Screen Saver]]<br />
* [[Dialer]] with [[Least Cost Routing]] for international calling<br />
* [[Headset Emulator]]<br />
<br />
=== 2nd Phase ===<br />
* [[Clocks]]<br />
* [[GPS Navigation]]<br />
* [[Calculator]]<br />
* [[Unit Converter]]<br />
* [[Game]]<br />
* [[Guitar Tuning]]<br />
* [[Code Memo]]<br />
* [[Video Player]]<br />
<br />
==Stylus-Based Applications ==<br />
<br />
=== 0th Phase ===<br />
* [[Top Panel]]<br />
* [[Footer]] with embedded [[History|Task Manager]]<br />
* [[Contacts]]<br />
* [[Calendar]]<br />
<br />
=== 1st Phase ===<br />
* [[Messages]]<br />
* [[Application Manager]]<br />
* [[Today]]<br />
* [[Feed Reader]]<br />
* [[Preferences]]<br />
* [[Help Viewer]]<br />
<br />
=== 2nd Phase ===<br />
* [[Search]]<br />
* [[Media Player]]<br />
* [[Sketchbook]]<br />
* [[Picture Viewer]]<br />
* [[File Browser]]<br />
* [[Terminal]]<br />
* [[IM]]<br />
* [[Web Browser]]<br />
* [[Reader]]<br />
* [[System Info]]<br />
<br />
== Panel Applications ==<br />
<br />
Panel Applications are individual executables residing in the [[Top Panel]]. They usually indicate their status and offer a pop-up menu. We are not yet sure whether there is enough screen real estate for this huge number of panel applications.<br />
<br />
=== 0th Phase ===<br />
* [[GSM & GPRS Connection Status]]<br />
* [[Battery Monitor]]<br />
* [[Clock]]<br />
<br />
=== 1st Phase ===<br />
* [[GPS Connection Status]]<br />
* [[Bluetooth Connection Status]]<br />
* [[USB Connection Status]]<br />
<br />
=== 2nd Phase ===<br />
* [[Search]]<br />
* [[IM Presence]]<br />
* [[Screen Grabber]]</div>Mikehttp://openmoko.org/wiki/ApplicationsApplications2007-02-18T15:44:58Z<p>Mike: </p>
<hr />
<div>== Overview ==<br />
Although [[OpenMoko]] is designed for smartphones that use a stylus, it would be foolish to expect people to only operate their handsets with stylus. For this reason, some core phone-related applications will be developed with finger (as opposed to stylus navigation) in mind.<br />
<br />
{{note| Applications listed on this page are listing in order of priority and by phase. 0th phase is for the developers preview release on February 11th, 1st phase is for March 11th. 2nd phase is September 11th...when we are ready for mass market appeal.}}<br />
<br />
<br />
== General Principles ==<br />
* All modifications are saved instantenously, there should never be a save command.<br />
* Make sure users can't make interface operation errors, or that the effects are easily reversible, instead of just notifying them of the potential consequences of their actions.<br />
* When you open a document you should be returned to the place where you were working when you last closed or save it (this is our concept of sessions).<br />
* Label buttons with adjectives, which describe the state of the object affected<br />
* Designers should seek an efficient monotonous solution to gain benefits, including ease of learning, simplicity of implementation, minimization of documentation, and lowered maintenance costs.<br />
* Whenever you find yourself specifying an error message, please stop; then redesign the interface so that the condition that generated the error message doesn't arise.<br />
* If the user gets no utility from a process, there is no reason to tell them that it is happening.<br />
<br />
{{note|Innovation usually happens at the bottom. What we need to do is provide consistent ways to develop and deploy appliations.}}<br />
<br />
==Finger-Based Applications ==<br />
<br />
=== 0th Phase ===<br />
* [[Dialer]]<br />
* [[Main Menu]]<br />
<br />
=== 1st Phase ===<br />
* [[Music Player]]<br />
* [[Screen Saver]]<br />
* [[Dialer]] with [[Least Cost Routing]] for international calling<br />
<br />
=== 2nd Phase ===<br />
* [[Clocks]]<br />
* [[GPS Navigation]]<br />
* [[Calculator]]<br />
* [[Unit Converter]]<br />
* [[Game]]<br />
* [[Guitar Tuning]]<br />
* [[Code Memo]]<br />
* [[Video Player]]<br />
<br />
==Stylus-Based Applications ==<br />
<br />
=== 0th Phase ===<br />
* [[Top Panel]]<br />
* [[Footer]] with embedded [[History|Task Manager]]<br />
* [[Contacts]]<br />
* [[Calendar]]<br />
<br />
=== 1st Phase ===<br />
* [[Messages]]<br />
* [[Application Manager]]<br />
* [[Today]]<br />
* [[Feed Reader]]<br />
* [[Preferences]]<br />
* [[Help Viewer]]<br />
<br />
=== 2nd Phase ===<br />
* [[Search]]<br />
* [[Media Player]]<br />
* [[Sketchbook]]<br />
* [[Picture Viewer]]<br />
* [[File Browser]]<br />
* [[Terminal]]<br />
* [[IM]]<br />
* [[Web Browser]]<br />
* [[Reader]]<br />
* [[System Info]]<br />
<br />
== Panel Applications ==<br />
<br />
Panel Applications are individual executables residing in the [[Top Panel]]. They usually indicate their status and offer a pop-up menu. We are not yet sure whether there is enough screen real estate for this huge number of panel applications.<br />
<br />
=== 0th Phase ===<br />
* [[GSM & GPRS Connection Status]]<br />
* [[Battery Monitor]]<br />
* [[Clock]]<br />
<br />
=== 1st Phase ===<br />
* [[GPS Connection Status]]<br />
* [[Bluetooth Connection Status]]<br />
* [[USB Connection Status]]<br />
<br />
=== 2nd Phase ===<br />
* [[Search]]<br />
* [[IM Presence]]<br />
* [[Screen Grabber]]</div>Mikehttp://openmoko.org/wiki/User:MikeUser:Mike2007-02-18T15:15:34Z<p>Mike: </p>
<hr />
<div>Living in the Rocky Mountains west of Denver, Colorado.<br />
<br />
I build and install custom PBX systems using GNU/Linux and Asterisk.<br />
<br />
I will be developing openmoko applications for specialized vertical markets.<br />
<br />
Michael Welter<br />
<br />
mike@introspect.com<br />
<br />
tel: +1 303 414 4978<br />
<br />
fax: +1 303 670 1918</div>Mikehttp://openmoko.org/wiki/Wish_List_-_HardwareWish List - Hardware2007-02-15T23:37:09Z<p>Mike: </p>
<hr />
<div>===Hardware enhancements===<br />
<br />
Some small hardware enhancement could be cheap, but very useful. Please add your ideas/wishes here:<br />
<br \><br />
=====Video-capable camera=====<br />
*preferably in rotatable turret set into top of unit, so it can face in either direction, making it useful for video conferencing<br />
<br />
=====Integrated WiFi hardware=====<br />
*To sync data<br />
*To access Internet when WiFi is available (at home, work, school, friends)<br />
*For VoIP (this uses much power but maybe the user have the charger connected)<br />
*for videoconferencing (as with AccessGrid)<br />
<br />
=====LED=====<br />
*A blinking LED would be cheap and low power, good for informing the user about new SMS/Email....<br />
**A simple alternative to this would be for one small segment of the LCD to be seperately backlit. There are typically many LEDs in the backlight, all normally on equally. This has the large advantage that you can display reasonable amounts of information on the bit of the screen that's illuminated. The disadvantage is the field of view is smaller, and it's comparatively dimmer, as the LCD absorbs some light.<br />
<br />
*Note: the LED and button ideas could be combined: illuminated buttons<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 />
=====Accelerometer===== <br />
*[[3D Viewport]]<br />
*[[Auto Align Map]]<br />
*[[Computer Mouse]]<br />
*[[Determine Position]]<br />
*[[Distance Measuring]]<br />
<br />
=====SIR transceiver=====<br />
*Could be used to detect when to turn of the display (if the low power IR signal is reflected) and activate the key lock. And could be used as a remote. iPhone has a proximity sensor.<br />
<br />
=====Standard 3.5mm jack=====<br />
<br />
=====Multitouch screen=====<br />
<br />
=====Multi I/O adapter=====<br />
*VGA, standard Jack (line in & out), standard USB<br />
<br />
=====MMC/SD/SDIO slot (rather than?) miniSD or microSD=====<br />
*Cheaper cards<br />
*More durable cards<br />
*Cards are harder to lose<br />
*Wider selection of accesories, including SDIO accessories.<br />
*More widely accepted format<br />
*Only because CF takes too much room (or CF would be the wish, instead)<br />
<br />
*See also [[Expansion Back]], replacement backs with additional features.<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 />
<br />
=====LASER keyboard (can be a full QWERTY keyboard)=====<br />
*someone knowing sth about the price?<br />
**This doesn't sound like it is likely to be cheap, and (at least for myself) I'm looking for a phone/pda/mp3 player, not for a very bad personal computer with a tiny screen that I can barely read. If it were cheap enough, I suppose it would not be a problem, but I doubt I'd pay a premium for it...--[[User:Perry|Perry]] 14:52, 15 February 2007 (CET)<br />
**I see. I thought sth. like that. In my opinion it would be better to implement an IrDA connector or use the bluetooth interface to connect to a small keyboard. So you could use it if you want but not everyone has to pay the price for such an exclusive feature --[[User:Denis std|denis_std]] 19:47, 15 February 2007 (CET)<br />
<br />
=====EDGE support=====<br />
<br />
=====Ability to insert more than one Sim-Card and (if possible) connect to more than one network at the same time=====<br />
<br />
=====RFID tag=====<br />
*Advantages of a RFID tag? I would see a lot privacy problems<br />
**The tag could be switched on or off. A nice feature would be a module able to clone tags. This would unfortunately probably be rather expensive.<br />
<br />
=====powered USB 2.0 host=====<br />
<br />
=====UMTS support=====<br />
<br />
=====Dump the '''''egg-shaped''''' case design and go '''''rectangular''''' for more screen space=====<br />
<br />
=====A standard slip-on or clip-on template (possibly with buttons) to make the touch-screen blind accessible=====<br />
<br />
=====Speakerphone functionality=====<br />
<br />
=====Reposition Speakers=====<br />
* putting the two speakers on opposite sides of the screen would make the stereo sound much more effective<br />
<br />
=====Small metal frame for protection (like Siemens M65, only with more style)=====<br />
<br />
=====free GPIO ports on a connector to allow easy, simple hardware extensions=====<br />
<br />
Sources:<br />
*http://www.linuxtogo.org/gowiki/OpenMoko/Hardware_wishes_for_next_versions<br />
<br />
=====Video acceleration=====<br />
Hardware acceleration for video playback.<br />
<br />
=====3D acceleration=====<br />
3D hardware acceleration for 3D games, GUIs, etc.<br />
<br />
=====Alcohol Sensor=====<br />
Alcohol sensor adjacent to microphone. It doesn't have to be accurate, just has to detect any amount of alcohol on the speaker's breath. I understand this is a very narrow market, but alcohol is on every parent's mind.</div>Mikehttp://openmoko.org/wiki/Wish_List_-_HardwareWish List - Hardware2007-02-15T22:03:08Z<p>Mike: </p>
<hr />
<div>===Hardware enhancements===<br />
<br />
Some small hardware enhancement could be cheap, but very useful. Please add your ideas/wishes here:<br />
<br \><br />
=====Video-capable camera=====<br />
*preferably in rotatable turret set into top of unit, so it can face in either direction, making it useful for video conferencing<br />
<br />
=====Integrated WiFi hardware=====<br />
*To sync data<br />
*To access Internet when WiFi is available (at home, work, school, friends)<br />
*For VoIP (this uses much power but maybe the user have the charger connected)<br />
*for videoconferencing (as with AccessGrid)<br />
<br />
=====LED=====<br />
*A blinking LED would be cheap and low power, good for informing the user about new SMS/Email....<br />
**A simple alternative to this would be for one small segment of the LCD to be seperately backlit. There are typically many LEDs in the backlight, all normally on equally. This has the large advantage that you can display reasonable amounts of information on the bit of the screen that's illuminated. The disadvantage is the field of view is smaller, and it's comparatively dimmer, as the LCD absorbs some light.<br />
<br />
*Note: the LED and button ideas could be combined: illuminated buttons<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 />
=====Accelerometer===== <br />
*[[3D Viewport]]<br />
*[[Auto Align Map]]<br />
*[[Computer Mouse]]<br />
*[[Determine Position]]<br />
*[[Distance Measuring]]<br />
<br />
=====SIR transceiver=====<br />
*Could be used to detect when to turn of the display (if the low power IR signal is reflected) and activate the key lock. And could be used as a remote. iPhone has a proximity sensor.<br />
<br />
=====Standard 3.5mm jack=====<br />
<br />
=====Multitouch screen=====<br />
<br />
=====Multi I/O adapter=====<br />
*VGA, standard Jack (line in & out), standard USB<br />
<br />
=====MMC/SD/SDIO slot (rather than?) miniSD or microSD=====<br />
*Cheaper cards<br />
*More durable cards<br />
*Cards are harder to lose<br />
*Wider selection of accesories, including SDIO accessories.<br />
*More widely accepted format<br />
*Only because CF takes too much room (or CF would be the wish, instead)<br />
<br />
*See also [[Expansion Back]]<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 />
<br />
=====LASER keyboard (can be a full QWERTY keyboard)=====<br />
*someone knowing sth about the price?<br />
**This doesn't sound like it is likely to be cheap, and (at least for myself) I'm looking for a phone/pda/mp3 player, not for a very bad personal computer with a tiny screen that I can barely read. If it were cheap enough, I suppose it would not be a problem, but I doubt I'd pay a premium for it...--[[User:Perry|Perry]] 14:52, 15 February 2007 (CET)<br />
**I see. I thought sth. like that. In my opinion it would be better to implement an IrDA connector or use the bluetooth interface to connect to a small keyboard. So you could use it if you want but not everyone has to pay the price for such an exclusive feature --[[User:Denis std|denis_std]] 19:47, 15 February 2007 (CET)<br />
<br />
=====EDGE support=====<br />
<br />
=====Ability to insert more than one Sim-Card and (if possible) connect to more than one network at the same time=====<br />
<br />
=====RFID tag=====<br />
*Advantages of a RFID tag? I would see a lot privacy problems<br />
**The tag could be switched on or off. A nice feature would be a module able to clone tags. This would unfortunately probably be rather expensive.<br />
<br />
=====powered USB 2.0 host=====<br />
<br />
=====UMTS support=====<br />
<br />
=====Dump the '''''egg-shaped''''' case design and go '''''rectangular''''' for more screen space=====<br />
<br />
=====A standard slip-on or clip-on template (possibly with buttons) to make the touch-screen blind accessible=====<br />
<br />
=====Speakerphone functionality=====<br />
<br />
=====Reposition Speakers=====<br />
* putting the two speakers on opposite sides of the screen would make the stereo sound much more effective<br />
<br />
=====Small metal frame for protection (like Siemens M65, only with more style)=====<br />
<br />
=====free GPIO ports on a connector to allow easy, simple hardware extensions=====<br />
<br />
Sources:<br />
*http://www.linuxtogo.org/gowiki/OpenMoko/Hardware_wishes_for_next_versions<br />
<br />
=====Video acceleration=====<br />
Hardware acceleration for video playback.<br />
<br />
=====3D acceleration=====<br />
3D hardware acceleration for 3D games, GUIs, etc.<br />
<br />
=====Alcohol Sensor=====<br />
Alcohol sensor adjacent to microphone. It doesn't have to be accurate, just has to detect any amount of alcohol on the speaker's breath.</div>Mike