Community Updates

From Openmoko

(Difference between revisions)
Jump to: navigation, search
m
 
(97 intermediate revisions by 26 users not shown)
Line 1: Line 1:
Even though Openmoko strives to keep the community informed of the development progress, OpenMoko does not provide delivery dates. Instead, Openmoko reports the project status here and on the [http://lists.openmoko.org/pipermail/community/ openmoko-community mailing list]. Major updates are also sent to the [http://lists.openmoko.org/pipermail/announce/ announce mailing list].
+
{{Languages}}
 +
This page gives you access to some regular updates released by the projects, OM or community. All communications channels of the Openmoko community are listed at the [[Community Resources]] page.  
  
You may also wish to take a look at the [http://gettingstartedopenmoko.wordpress.com/ Getting started with OpenMoko blog].
+
The official Openmoko updates (discontinued early 2009) can be found in [[Weekly Engineering News]].
  
Interested developers may additionally wish to follow the progress on the [http://lists.openmoko.org/pipermail/openmoko-kernel/ openmoko-kernel mailing list].
+
You can see the latest edition [[Community_Updates/current]]
  
You are invited to add questions or topics you think should be included in the Community Updates by emailing community@lists.openmoko.org or by editing section 2 of this wiki page.
+
= Post launch series =
 +
* [[Community Updates/Draft]]
 +
* [[Community Updates/2011-12-01]]
 +
* [[Community Updates/2011-09-01]]
 +
* [[Community Updates/2011-05-01]]
 +
* [[Community Updates/2011-03-01]]
 +
* [[Community Updates/2011-02-01]]
 +
* [[Community Updates/2010-12-01]]
 +
* [[Community Updates/2010-11-01]]
 +
* [[Community Updates/2010-09-01]]
 +
* [[Community Updates/2010-08-01]]
 +
* [[Community Updates/2010-07-01]]
 +
* [[Community Updates/2010-06-01]]
 +
* [[Community Updates/2010-05-01]]
 +
* [[Community Updates/2010-04-01]]
 +
* [[Community Updates/2010-03-01]]
 +
* [[Community Updates/2010-02-10]]
 +
* [[Community Updates/2010-01-14]]
 +
* [[Community Updates/2009-12-31]]
 +
* [[Community Updates/2009-12-09]]
 +
* [[Community Updates/2009-11-25]]
 +
* [[Community Updates/2009-11-11]]
 +
* [[Community Updates/2009-10-28]]
 +
* [[Community Updates/2009-10-14]]
 +
* [[Community Updates/2009-09-30]]
 +
* [[Community Updates/2009-09-16]]
 +
* [[Community Updates/2009-09-02]]
 +
* [[Community Updates/2009-08-19]]
 +
* [[Community Updates/2009-08-06]]
 +
* [[Community Updates/2009-07-23]]
 +
* [[Community Updates/2009-07-09]]
 +
* [[Community Updates/2009-06-25]]
 +
* [[Community Updates/2009-05-22]]
 +
* [[Community Updates/2009-04-30]]
 +
* [[Community Updates/2009-04-17]]
 +
* [[Community Updates/2009-04-05]]
 +
* [[Community Updates/2009-03-20]]
 +
* [[Community Updates/2009-03-06]]
 +
* [[Community Updates/2009-02-20]]
 +
* [[Community Updates/2009-02-06]]
 +
* [[Community Updates/2009-01-23]]
 +
* [[Community Updates/2009-01-12]]
 +
* [[Community Updates/2008-12-29]]
 +
* [[Community Updates/2008-12-15]]
 +
* [[Community Updates/2008-12-01]]
 +
* [[Community Updates/2008-11-16]]
 +
* [[Community Updates/2008-11-02]]
 +
* [[Community Updates/2008-10-19]]
 +
* [[Community Updates/2008-10-03]]
 +
* [[Community Updates/2008-09-17]] - Activity since launch
  
The latest Community Update was posted to the community mailing list on [http://lists.openmoko.org/pipermail/community/2008-June/019384.html 14th June, 2008 - When it will be possible to buy OpenMoko?].
+
== Rules for community updates ==
 +
After May 22nd 2009 OM stopped working on community updates. These rules are here to make it possible for the community to keep the updates running.
  
'''Steve said''':
+
The draft of the news will be listed here but not on the main page until it gets released. (example, see [[Community Updates/Draft]] ). Upon the release of the current updates a new page should be created. The news will be added there. On release, the link will be set on the main page. Detailed instructions below.
SMT is running. This means printed circuit boards are being produced daily.
+
+
Then, the circuit boards are being assembled into phones. This means the
+
plastic casing is being mounted
+
As well as other bits and pieces.
+
+
Then the phones are tested. Then they are packed and shipped.
+
+
So figure, assembly is going to start in the week of june 16, pack and ship
+
by june 23
+
Arrive and clear customs by july 1.
+
+
Hey 4th of july sale! Sorry american bias. But I'd figure early july.  
+
  
 +
'''Adding news'''
 +
# Don't expect someone else to add it, add it yourself and make it nice
 +
# Add links to blog posts, applications, mailing list posts that you think are worth to announce to the whole community
  
  FreeRunners are '''shipping now''' in the EU from resellers.  This is not official in any way, but
+
'''Releasing'''
  the [http://www.openmoko.com Openmoko store] is rumored to open on July 7.
+
# If it's The Release Date and you notice the news has not been released, DO IT! Don't expect someone else to do it for you.
 +
# When you release, move the content of Talk: page to the actual wikipage.
 +
# Add a link to the released update page to http://wiki.openmoko.org/index.php?title=Community_Updates
 +
# Prepare the draft page for the next community news: captions, dates etc.. Releasing news on Thursdays every two weeks sound's good to me.
 +
# Send a post to the community mailing list with the link to the released news and the draft of the next news.
  
See [[Community_Updates#Previous_Community_Updates | below]] for a list of previous updates.
+
= Ramp up to launch series =
  
 +
Even though Openmoko strives to keep the community informed of the development progress, Openmoko does not provide delivery dates. Instead, Openmoko Inc. reports and discusses the project on a day to day basis, using the [http://lists.openmoko.org/pipermail/community/ openmoko-community mailing list]. Developers will wish to follow the progress on the [http://lists.openmoko.org/pipermail/openmoko-kernel/ openmoko-kernel mailing list] and the [http://lists.openmoko.org/pipermail/devel/ devel mailing list]. Major updates notices are sent to the [http://lists.openmoko.org/pipermail/announce/ announce mailing list].
  
==Discussion of current issues ==
+
As FreeRunners started shipping, that series of Community Updates mostly related to the expected release date has been taken over by a more community-oriented newsletter.
<!--- this summary was updated by community members because it was not updated by [[User:Michaelshiloh|Michael Shiloh]]--->
+
  
 +
* [http://lists.openmoko.org/pipermail/community/2008-June/019384.html 2008-06-14 - When it will be possible to buy Openmoko?]
 +
* [http://lists.openmoko.org/pipermail/community/2008-June/018887.html 2008-06-10 - SMT is running!]
 +
* [http://lists.openmoko.org/pipermail/community/2008-June/018575.html 2008-06-05 - Cleared to start Mass production]
 +
* [http://lists.openmoko.org/pipermail/community/2008-May/017531.html 2008-05-20 - Whats up with the freerunner mass production?]
 +
* [http://lists.openmoko.org/pipermail/community/2008-April/015189.html 2008-04-14 - next costumers location]
 +
* [http://lists.openmoko.org/pipermail/community/2008-April/015080.html 2008-04-11 - FreeRunner Pricing and PVT update]
 +
* [http://lists.openmoko.org/pipermail/community/2008-April/014928.html 2008-04-07 - Any updates on the PVT status?]
 +
* [http://lists.openmoko.org/pipermail/community/2008-March/014361.html 2008-03-25 - Production status Update]
 +
* [http://lists.openmoko.org/pipermail/community/2008-February/013555.html 2008-02-25 - Community Update]
 +
* [http://lists.openmoko.org/pipermail/community/2008-February/013356.html 2008-02-14 - Community Update]
 +
* [http://lists.openmoko.org/pipermail/community/2008-February/013280.html 2008-02-10 - Community Update]
 +
* [http://lists.openmoko.org/pipermail/community/2008-January/012821.html 2008-01-24 - Community Update]
 +
* [http://lists.openmoko.org/pipermail/community/2008-January/012499.html 2008-01-10 - Community Update]
 +
* [http://lists.openmoko.org/pipermail/community/2008-January/012357.html 2008-01-02 - Community Update]
  
 
+
[[Category:Community Update| ]]
===GTA02 hardware design and test===
+
The information below has been collected from various sources, feel free to add questions and comments here.
+
 
+
While writing a device driver for the new battery which provides an accurate counter of the charge state of the [[GTA02]], the driver developer discovered that the device driver does not get a reading of the charge state due to a very long response time with only one I/O signal when trying to read the charge state. To be able to read the battery status properly, it has been written that it will be necessary to re-design that part of the GTA02 for hardware version GTA02A5 to use two I/O signals to reduce the response time (one for transmitting commands, one for receiving data?). [http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=957#c1 Bug 957] may have more information.
+
 
+
12/06/2007 - GTA02a5 is a minor variation from GTA02a4, so it shouldn't take very long. We are waiting for confirmation of Wifi and a few other parts of the GTA02a4 hardware before we manufacture even a small test run of GTA02a5.
+
 
+
01/30/2008 - A small number of GTA02A5 have been made and are now being tested. Since much of the hardware is being verified by kernel and driver code, an excellent place to monitor this is on the openmoko-kernel mailing list.
+
 
+
03/18/2008 - The Freerunner design is currently staged to go through Production
+
Validation Test (PVT). The hardware design A5 is, we believe, solid. We are updating this design to A6 to maximize production yields.
+
 
+
The purpose of PVT is to make sure the yield is high enough, and to make sure the manufacturing and testing process is smooth and efficient.
+
 
+
===gllin GPS driver for GTA01===
+
11/29/2007 - Thanks to a tremendous amount of hard work by many people, we have ready
+
a release of gllin, the GPS driver. Instructions at [http://lists.openmoko.org/pipermail/community/2007-November/011916.html] or grab the ipk directly from [http://3rdparty.downloads.openmoko.org/gllin/].
+
 
+
===850 MHz band not supported in USA+Canada (e.g. comment 24 on bug #256)===
+
 
+
The GSM chip set is capable of quad band operation but the circuit implemented in GTA02 only supports 3 bands. Currently GTA02 supports only 900/1800/1900MHz.
+
 
+
11/29/2007 - We would like to offer an 850/1800/1900MHz version of GTA02 for areas that need it. We are looking into whether this is feasible or not. This requires a number of changes (components, firwmare, calibration, etc.) and so is uncertain until we test it.
+
 
+
12/09/2007 - Since the GSM section is essentially the same between GTA01 and GTA02, we thought a good experiment would be to modify a couple GTA01 handsets for 850MHz and to test them out here in the USA.
+
 
+
12/20/2007 - Due to the enthusiastic response I received to my request for testing volunteers I've asked our hardware group to modify a few more phones. I don't know when, or even if, they will be able to do this. Meanwhile, I'll be sending out the units I have to the testers, along with a simple test plan.
+
 
+
We have no intention of manufacturing 850MHz GTA01s, nor can we modify user's phones this way. We modified a couple of units ONLY so that we could test the circuit that we might use in GTA02. When the experiment is done, these modified units must be returned to OpenMoko.
+
 
+
Conversion of GTA02 to quad band would require major changes and so will not happen.
+
 
+
===Delivery of a GSM firmware update for the 3G SIM bug ([http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=666 #666])===
+
Background:
+
 
+
A bug in the GSM firmware prevents some USA 3G SIM cards from working properly. The bug has been fixed, but since the GSM module is under extremely tight legal protection, it is not clear whether or how we can allow customers to perform this upgrade themselves.
+
 
+
12/09/2007 - We've been informed that everything legal has been agreed upon by all parties regarding the process that would allow you to upgrade your own GSM firmware. All that remains is to get everything signed. Apparently the process of getting things signed takes a few weeks!
+
 
+
12/20/2007 - Meanwhile, we have resolved the difficulties I was having performing the upgrade, and I am now able to upgrade your handsets. Anyone interested in having me do this should contact me at michael@openmoko.org.
+
 
+
==Questions or Topics you think are missing==
+
 
+
===Touch screen & the screen itself===
+
What about talking with the touch screen? There doesn't seem to be any kind of proximity sensor to feel the presence of ear + cheek to disable the touch screen, so error presses can be an issue. I feel the need to both be able to talk with the phone on my ear and still be able to use the programs while calling so simply disabling touch screen while talking can't be a possibility. I've heard multiple possibilities to remedy this with shaking the phone to enable/disable touch screen and et cetera, but none of them have been easy enough for everyday use. It '''has''' to work seamlessly.
+
 
+
Also, some of the photos I've seen of the device have shown a significant amount of glare in the screen. Will the screen be usable at all outdoors in sunny weather? There should be an anti-glare & anti-scratch coating on the screen. The useability of the screen ''especially when it's the only UI for using the device'' is fundamental and IMO its importance goes beyond almost all other features. If one can't see what's on the screen for half of the time and has to cover it with hands or go into shade in order to be able to use the phone, what good is it? Has anyone made a study on the screen yet?
+
http://wiki.openmoko.org/wiki/Neo_FreeRunner_GTA02_Hardware#Display
+
 
+
=== SMedia 3362 Documentation & OpenGL ES Drivers ===
+
There is an open source kdrive driver being written for the GTA02 which will use hardware to accelerate the XRender extension. While the chip is capable of 3D graphics, no OpenGL ES driver/library is avaliable and OpenMoko developers will not be writing one in the near future (although they have not ruled it out in the long-term).
+
 
+
Documentation for the SMedia 3362 has been promised ([http://lists.openmoko.org/pipermail/community/2007-September/010175.html see this post]). However, this refers to documentation OpenMoko developers will be writing themselves, not the technical documentation SMedia have provided OpenMoko with. The OpenMoko developers had to sign an NDA with SMedia to obtain this documentation and are therefore unable to pass this information on to community developers. (See [http://lists.openmoko.org/pipermail/community/2007-November/011349.html this post] for details)
+
 
+
=== Power Management on the Neo1973===
+
It is still not clear if it will be possible to have "reasonable" battery life on the Neo1973 (GTA1) hardware or if there are hardware problems that make  this impossible.([http://lists.openmoko.org/pipermail/community/2008-January/012456.html  see this post]). Can this be officially clarified?
+
 
+
Further questions and comments regarding this by a GTA01 Neo owner:
+
 
+
This is the single most important issue keeping european users (not affected by the 850MHz issues) from using the neo as a regular phone. After reading in various places (IRC, Lists, this Wiki), it seems like this issue divides into several ones and a more detailed answer would be helpful for each:
+
 
+
* if it's a bug in the firmware failing to trigger an IRQ, is at least the kernel sufficiently prepared to wake up?
+
* there are rumours that a wrong resistor value on the GTA01 board yields a very high quiescient current for the GSM in suspend mode. Is there any further information on this (what's the battery life in proper suspend with and without this fix) and maybe a short document describing a fix available? Is it doable at home (replacing a 0402 surely counts as doable!)
+
* what is the status of failed resumes after a suspend?
+
 
+
'''Another''' vote for power management, Neo is practically useless with all the configurability and features if it needs to be plugged on a charger every day. I'm expecting more from Neo in terms of power management and battery life time than from for example E90 which is packed with many hw and sw features. I hope the hardware is re-checked so that these kind of errors in the design (unreasonably high currents etc) get worked out.
+
 
+
==Previous Community Updates==
+
*[[September 28, 2007 Community Update]]
+
*[[October 12, 2007 Community Update]]
+
*[[October 13, 2007 Community Update]]
+
*[[October 15, 2007 Community Update]]
+
*[[October 16, 2007 Community Update]]
+
*[[October 25, 2007 Community Update]]
+
*[[October 31, 2007 Community Update]]
+
*[[November 6, 2007 Community Update]]
+
*[[November 13, 2007 Community Update]]
+
*[[November 26, 2007 Community Update]]
+
*[[November 29, 2007 Community Update]]
+
*[[December 09, 2007 Community Update]]
+
*[[December 20, 2007 Community Update]]
+
*[http://lists.openmoko.org/pipermail/community/2008-January/012357.html January 2, 2008 - Community Update]
+
*[http://lists.openmoko.org/pipermail/community/2008-January/012499.html January 10, 2008 - Community Update]
+
*[http://lists.openmoko.org/pipermail/community/2008-January/012821.html January 24, 2008 - Community Update]
+
*[http://lists.openmoko.org/pipermail/community/2008-February/013280.html February 10, 2008 - Community Update]
+
*[http://lists.openmoko.org/pipermail/community/2008-February/013356.html February 14, 2008 - Community Update]
+
*[http://lists.openmoko.org/pipermail/community/2008-February/013555.html February 25, 2008 - Community Update]
+
* [http://lists.openmoko.org/pipermail/community/2008-March/014361.html March 25, 2008 - Production status Update]
+
* [http://lists.openmoko.org/pipermail/community/2008-April/014928.html April 7, 2008 - Any updates on the PVT status?]
+
* [http://lists.openmoko.org/pipermail/community/2008-April/015080.html April 11, 2008 - FreeRunner Pricing and PVT update]
+
* [http://lists.openmoko.org/pipermail/community/2008-April/015189.html April 14, 2008 - next costumers location]
+
* [http://lists.openmoko.org/pipermail/community/2008-May/017531.html May 20, 2008 - Whats up with the freerunner mass production?]
+
* [http://lists.openmoko.org/pipermail/community/2008-June/018575.html 5th June, 2008 - Cleared to start Mass production]
+
* [http://lists.openmoko.org/pipermail/community/2008-June/018887.html 10th June, 2008 - SMT is running!]
+
 
+
 
[[Category:Community]]
 
[[Category:Community]]
[[Category:Information]]
 

Latest revision as of 06:50, 25 November 2011

This page gives you access to some regular updates released by the projects, OM or community. All communications channels of the Openmoko community are listed at the Community Resources page.

The official Openmoko updates (discontinued early 2009) can be found in Weekly Engineering News.

You can see the latest edition Community_Updates/current

[edit] Post launch series

[edit] Rules for community updates

After May 22nd 2009 OM stopped working on community updates. These rules are here to make it possible for the community to keep the updates running.

The draft of the news will be listed here but not on the main page until it gets released. (example, see Community Updates/Draft ). Upon the release of the current updates a new page should be created. The news will be added there. On release, the link will be set on the main page. Detailed instructions below.

Adding news

  1. Don't expect someone else to add it, add it yourself and make it nice
  2. Add links to blog posts, applications, mailing list posts that you think are worth to announce to the whole community

Releasing

  1. If it's The Release Date and you notice the news has not been released, DO IT! Don't expect someone else to do it for you.
  2. When you release, move the content of Talk: page to the actual wikipage.
  3. Add a link to the released update page to http://wiki.openmoko.org/index.php?title=Community_Updates
  4. Prepare the draft page for the next community news: captions, dates etc.. Releasing news on Thursdays every two weeks sound's good to me.
  5. Send a post to the community mailing list with the link to the released news and the draft of the next news.

[edit] Ramp up to launch series

Even though Openmoko strives to keep the community informed of the development progress, Openmoko does not provide delivery dates. Instead, Openmoko Inc. reports and discusses the project on a day to day basis, using the openmoko-community mailing list. Developers will wish to follow the progress on the openmoko-kernel mailing list and the devel mailing list. Major updates notices are sent to the announce mailing list.

As FreeRunners started shipping, that series of Community Updates mostly related to the expected release date has been taken over by a more community-oriented newsletter.

Personal tools

Even though Openmoko strives to keep the community informed of the development progress, OpenMoko does not provide delivery dates. Instead, Openmoko reports the project status here and on the openmoko-community mailing list. Major updates are also sent to the announce mailing list.

You may also wish to take a look at the Getting started with OpenMoko blog.

Interested developers may additionally wish to follow the progress on the openmoko-kernel mailing list.

You are invited to add questions or topics you think should be included in the Community Updates by emailing community@lists.openmoko.org or by editing section 2 of this wiki page.

The latest Community Update was posted to the community mailing list on 14th June, 2008 - When it will be possible to buy OpenMoko?.

Steve said:

SMT is running. This means printed circuit boards are being produced daily.

Then, the circuit boards are being assembled into phones. This means the
plastic casing is being mounted
As well as other bits and pieces.

Then the phones are tested. Then they are packed and shipped.

So figure, assembly is going to start in the week of june 16, pack and ship
by june 23
Arrive and clear customs by july 1.

Hey 4th of july sale! Sorry american bias. But I'd figure early july. 


 FreeRunners are shipping now in the EU from resellers.  This is not official in any way, but
 the Openmoko store is rumored to open on July 7.

See below for a list of previous updates.


Discussion of current issues

GTA02 hardware design and test

The information below has been collected from various sources, feel free to add questions and comments here.

While writing a device driver for the new battery which provides an accurate counter of the charge state of the GTA02, the driver developer discovered that the device driver does not get a reading of the charge state due to a very long response time with only one I/O signal when trying to read the charge state. To be able to read the battery status properly, it has been written that it will be necessary to re-design that part of the GTA02 for hardware version GTA02A5 to use two I/O signals to reduce the response time (one for transmitting commands, one for receiving data?). Bug 957 may have more information.

12/06/2007 - GTA02a5 is a minor variation from GTA02a4, so it shouldn't take very long. We are waiting for confirmation of Wifi and a few other parts of the GTA02a4 hardware before we manufacture even a small test run of GTA02a5.

01/30/2008 - A small number of GTA02A5 have been made and are now being tested. Since much of the hardware is being verified by kernel and driver code, an excellent place to monitor this is on the openmoko-kernel mailing list.

03/18/2008 - The Freerunner design is currently staged to go through Production Validation Test (PVT). The hardware design A5 is, we believe, solid. We are updating this design to A6 to maximize production yields.

The purpose of PVT is to make sure the yield is high enough, and to make sure the manufacturing and testing process is smooth and efficient.

gllin GPS driver for GTA01

11/29/2007 - Thanks to a tremendous amount of hard work by many people, we have ready a release of gllin, the GPS driver. Instructions at [1] or grab the ipk directly from [2].

850 MHz band not supported in USA+Canada (e.g. comment 24 on bug #256)

The GSM chip set is capable of quad band operation but the circuit implemented in GTA02 only supports 3 bands. Currently GTA02 supports only 900/1800/1900MHz.

11/29/2007 - We would like to offer an 850/1800/1900MHz version of GTA02 for areas that need it. We are looking into whether this is feasible or not. This requires a number of changes (components, firwmare, calibration, etc.) and so is uncertain until we test it.

12/09/2007 - Since the GSM section is essentially the same between GTA01 and GTA02, we thought a good experiment would be to modify a couple GTA01 handsets for 850MHz and to test them out here in the USA.

12/20/2007 - Due to the enthusiastic response I received to my request for testing volunteers I've asked our hardware group to modify a few more phones. I don't know when, or even if, they will be able to do this. Meanwhile, I'll be sending out the units I have to the testers, along with a simple test plan.

We have no intention of manufacturing 850MHz GTA01s, nor can we modify user's phones this way. We modified a couple of units ONLY so that we could test the circuit that we might use in GTA02. When the experiment is done, these modified units must be returned to OpenMoko.

Conversion of GTA02 to quad band would require major changes and so will not happen.

Delivery of a GSM firmware update for the 3G SIM bug (#666)

Background:

A bug in the GSM firmware prevents some USA 3G SIM cards from working properly. The bug has been fixed, but since the GSM module is under extremely tight legal protection, it is not clear whether or how we can allow customers to perform this upgrade themselves.

12/09/2007 - We've been informed that everything legal has been agreed upon by all parties regarding the process that would allow you to upgrade your own GSM firmware. All that remains is to get everything signed. Apparently the process of getting things signed takes a few weeks!

12/20/2007 - Meanwhile, we have resolved the difficulties I was having performing the upgrade, and I am now able to upgrade your handsets. Anyone interested in having me do this should contact me at michael@openmoko.org.

Questions or Topics you think are missing

Touch screen & the screen itself

What about talking with the touch screen? There doesn't seem to be any kind of proximity sensor to feel the presence of ear + cheek to disable the touch screen, so error presses can be an issue. I feel the need to both be able to talk with the phone on my ear and still be able to use the programs while calling so simply disabling touch screen while talking can't be a possibility. I've heard multiple possibilities to remedy this with shaking the phone to enable/disable touch screen and et cetera, but none of them have been easy enough for everyday use. It has to work seamlessly.

Also, some of the photos I've seen of the device have shown a significant amount of glare in the screen. Will the screen be usable at all outdoors in sunny weather? There should be an anti-glare & anti-scratch coating on the screen. The useability of the screen especially when it's the only UI for using the device is fundamental and IMO its importance goes beyond almost all other features. If one can't see what's on the screen for half of the time and has to cover it with hands or go into shade in order to be able to use the phone, what good is it? Has anyone made a study on the screen yet? http://wiki.openmoko.org/wiki/Neo_FreeRunner_GTA02_Hardware#Display

SMedia 3362 Documentation & OpenGL ES Drivers

There is an open source kdrive driver being written for the GTA02 which will use hardware to accelerate the XRender extension. While the chip is capable of 3D graphics, no OpenGL ES driver/library is avaliable and OpenMoko developers will not be writing one in the near future (although they have not ruled it out in the long-term).

Documentation for the SMedia 3362 has been promised (see this post). However, this refers to documentation OpenMoko developers will be writing themselves, not the technical documentation SMedia have provided OpenMoko with. The OpenMoko developers had to sign an NDA with SMedia to obtain this documentation and are therefore unable to pass this information on to community developers. (See this post for details)

Power Management on the Neo1973

It is still not clear if it will be possible to have "reasonable" battery life on the Neo1973 (GTA1) hardware or if there are hardware problems that make this impossible.(see this post). Can this be officially clarified?

Further questions and comments regarding this by a GTA01 Neo owner:

This is the single most important issue keeping european users (not affected by the 850MHz issues) from using the neo as a regular phone. After reading in various places (IRC, Lists, this Wiki), it seems like this issue divides into several ones and a more detailed answer would be helpful for each:

  • if it's a bug in the firmware failing to trigger an IRQ, is at least the kernel sufficiently prepared to wake up?
  • there are rumours that a wrong resistor value on the GTA01 board yields a very high quiescient current for the GSM in suspend mode. Is there any further information on this (what's the battery life in proper suspend with and without this fix) and maybe a short document describing a fix available? Is it doable at home (replacing a 0402 surely counts as doable!)
  • what is the status of failed resumes after a suspend?

Another vote for power management, Neo is practically useless with all the configurability and features if it needs to be plugged on a charger every day. I'm expecting more from Neo in terms of power management and battery life time than from for example E90 which is packed with many hw and sw features. I hope the hardware is re-checked so that these kind of errors in the design (unreasonably high currents etc) get worked out.

Previous Community Updates