request for documentation page and location to put it
steve at openmoko.com
Sun Aug 3 21:32:59 CEST 2008
The problem is everyone abuses the main page by trying to grab focus.
The problem is people trying to "main page" things to get attention
And they do this because
A. there is no logical structure
B. There is no search.
So, you have a haphazard, stuff it in the corner, or under the bed, or throw
it on the main page method of organization.
From: Michael Shiloh [mailto:michael at openmoko.org]
Sent: Friday, August 01, 2008 7:56 PM
To: openmoko documentation; steve
Subject: request for documentation page and location to put it
Many people come to the wiki when something doesn't work. I've been trying
to figure out the best way to help them, and I've come up with this idea.
Please tell me what you think:
1. Have a "known issues" section prominently displayed on the main page,
perhaps near the top.
2. Each known issue should include the symptoms and a diagnostic (so that a
user can determine whether the problem they are experiencing is in fact this
known issue). Diagnostics might be sparse when an issue first becomes known,
and will become clearer as we learn about the issue.
3. Each known issue will also (hopefully :-) feature a solution section,
although initially it might be empty.
4. After a known issue is solved, and the patches are present in daily
builds, and enough time has elapsed to prove it is really solved the issue
must be removed from the "known issues" section so that the wiki remains
This also raises the question of historical items. Once things are over and
done, removing from the wiki would avoid confusion. On the other hand,
history is good. Not sure how best to handle this, but it's lower priority I
-------- Original Message --------
Subject: FW: Sim card is not working, how do I run diagnostics?
Date: Sun, 20 Jul 2008 14:32:02 -0700
From: steve <steve at openmoko.com>
To: William Lai <will at openmoko.com>, Neng-Yu Tu (Tony Tu)
<tony at openmoko.com>, Michael Shiloh <michael at openmoko.org>
CC: Sean Moss-Pultz <sean at openmoko.com>
We need a place where people can go to get this informtion
Wiki is NOT good enough
Mailing list is a nightmare, like asking the sphinx.
From: community-bounces at lists.openmoko.org
[mailto:community-bounces at lists.openmoko.org] On Behalf Of Adam Talbot
Sent: Friday, July 11, 2008 3:23 PM
To: List for Openmoko community discussion
Subject: Re: Sim card is not working, how do I run diagnostics?
And I am stuck
I have 3 brand new sim cards.
None of which work in my FreeRunner. What does the reading of the SIM?
How do I look at that for bugs, and perhaps a bug fix. What is needed on
the SIM, is it just the S/N? Can I reprogram a S/N for an unactivated card
to one of my old working chips? Then call AT&T and get it activated?
On Thu, 2008-07-10 at 22:39 -0700, Adam Talbot wrote:
> I am a tinker, left on my own (+google) I can figure out almost
> anything :-)
> Sim cards. Here is the "how to" check.
> Follow this until you get an OK prompt.
> >From there your first command should be at+cimi. If it returns the
> of your card, you have a working card. If not (ERROR), you are out of
> Here are the cards I tested:
> AT&T, blue front, purple/blue-green back. Worked.
> AT&T, All white. Worked.
> Cingular, 73000O (4021) Worked.
> Cingular, 63512A (1002) Worked. FR hung on boot, may be unrelated.
> Reboot fixed it.
> AT&T, 71234G (3022) I have two, both failed.
> Should there be a global SIM card compatibility section? Like this,
> just MUCH bigger?
> I am running a Freerunner +
.jffs2, my provider is AT&T, out of California.
> Hope this helps.
> On Thu, 2008-07-10 at 19:59 -0700, Adam Talbot wrote:
> > My sim card is not working, how do I run diagnostics? I was looking
> > on the Wiki, but searching for sim turns up nothing worth while. I
> > have a pile of sim card to work with, each different. Would love to
> > test them out. Where is the "how to"?
> > -Adam
> Openmoko community mailing list
> community at lists.openmoko.org
Openmoko community mailing list
community at lists.openmoko.org
More information about the documentation