FSO & Android (was: Sad Story)

[Wolfgang Spraul]

Paul,

> create a working phone.  Passing the buck to FSO is passing the torch
> to someone else.  This is what OM has done.

We are funding FSO. This is called teamwork :-)
FSO concentrates on the framework, and standardizing interfaces for  
mobile phones. FSO = freesmartphone.org
Openmoko concentrates engineering on the lower level (kernel &  
drivers), as well as on the top-most level (UI design).
All of this is made possible by our community buying our phones and  
helping with development everywhere.

> I'm sure the majority of hardware owners are awaiting Google Android.

The cool thing about Free Software is it's configurability and  
modularity.
Try to build a product with half of Android. Won't work. Half of  
Debian, let alone any image generated with OpenEmbedded? No problem.

Best Regards,
Wolfgang

On Dec 16, 2008, at 3:47 AM, Paul wrote:

> Seeing the responses to criticism, it is clear why OpenMoko is where
> it is today.  If a significant portion of the community is frustrated
> at the status of this project, the best course of action is to address
> the concerns of the community.  Does telling people to buy an iphone
> accomplish anything but lower your social standing on this list?
>
> The main reason of why Open Source works is because people are able to
> criticize.  When the criticisms are taken into account, real progress
> can be had.
>
> We as a community were warned of the alpha status of the phone.  What
> we expected was that the community and company would work hand in hand
> to create a viable phone solution.  Yet, it is clear that the resolve
> of the Company is waning and the rest of the community is left holding
> the bag.  Now we have people blaming us because we are holding the
> bag.
>
> Just because a project is Open Source, doesn't guarantee its success.
> We have a lot of people working hard to resolve issues, yet we haven't
> achieved our goal.  We need to refocus our goals and objectives to
> create a working phone.  Passing the buck to FSO is passing the torch
> to someone else.  This is what OM has done.
>
> I'm sure the majority of hardware owners are awaiting Google Android.
> -- 
> Paul
> Email - pault...@gmail.com
>
> There were moments when he looked on evil simply as a mode through
> which he could realize his conception of the beautiful.
> Oscar Wilde - The Picture of Dorian Gray
>
> ___
> support mailing list
> support@lists.openmoko.org
> https://lists.openmoko.org/mailman/listinfo/support


___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: Sad Story

[Karthik Kumar]

>From now on, I'm listening only if it's a complaint, or if Openmoko is
fixing something on GTA02. I couldn't care less if Openmoko's moving
on, because I'm moving on.

Oh, the community's messages isn't going under my radar at all;
Because if it's going legal, _ONLY_ Openmoko is going to get it's ass
kicked. That will show them the reality of business and this world. If
anybody not from Openmoko is hijacking this thread believing I am
attacking the community at large, they are just foolish and putting
unneccessary effort upon themselves.

And Oh: I do not care if I'm getting shunned by you, you're putting me
on ignore, or asking me to  buy an iPhone, because I am primarily
conversing ONLY with Openmoko. From now on, I wouldn't care to return
non-Openmoko-ers insults.

If Openmoko is going to sort out specific GTA02 problems within this
year, send it out. Since Openmoko's release this July, it's been
nothing but utter disappointment and sheer carelessness from
Openmoko's side. And if it's all lies and greed, I don't believe in
Karma, I believe in legal course. If someone else is also interested
in class-action, pvt. me and we'll see what their 'business' is all
about.

Thanks All.

-Karthik

___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: Sad Story

[Karthik Kumar]

Instead of just bitching about me, why don't you do something
constructive, dipshit^U?

On Tue, Dec 16, 2008 at 10:09 AM, Joel Newkirk  wrote:
> On Tue, 16 Dec 2008 09:43:32 +1100, Dale Maggee 
> wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Karthik Kumar wrote:
 I know better.
>>
>> I could debate that at great length, cuz it's pretty god damn obvious to
>> us all that you don't know shit, but I've had a better Idea - I'm just
>> gonna create a filter to automatically delete anything sent by you. I
>> hope for your sake you never have a problem with NeoTool.
>>
>> bye now.
>
> I did that several days ago - he joined 'dip^H^H^Hnishit dave' in my filter
> list.
>
> nothing like a good old fashioned shunning.  :)
>
> j
>
> --
> Joel Newkirk
> http://jthinks.com  (blog)
> http://newkirk.us/om (FR stuff)
>
>
> ___
> support mailing list
> support@lists.openmoko.org
> https://lists.openmoko.org/mailman/listinfo/support
>



-- 
Karthik
http://guilt.bafsoft.net

___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: Sad Story

[Joel Newkirk]

On Tue, 16 Dec 2008 09:43:32 +1100, Dale Maggee 
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> Karthik Kumar wrote:
>>> I know better.
> 
> I could debate that at great length, cuz it's pretty god damn obvious to
> us all that you don't know shit, but I've had a better Idea - I'm just
> gonna create a filter to automatically delete anything sent by you. I
> hope for your sake you never have a problem with NeoTool.
> 
> bye now.

I did that several days ago - he joined 'dip^H^H^Hnishit dave' in my filter
list.

nothing like a good old fashioned shunning.  :)

j

-- 
Joel Newkirk
http://jthinks.com  (blog)
http://newkirk.us/om (FR stuff)


___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: SHR - GPRS

[Al Johnson]

On Monday 15 December 2008, Paul wrote:
> Thank you for your response.
>
> I honestly do not know where to begin.  I am not receiving an error,
> it's just not connecting.  I did try the internet and it is not
> connecting.

fso-config-util.py just provides a GUI that passes parameters to 
org.freesmartphone.GSM.PDP.ActivateContext() and shows the output of the 
ContextStatus signal, in your case 'release'. I should probably make it more 
human-readable, but in the meantime you can find an explanation at 
http://docs.freesmartphone.org

You should be able to enable logging for fso in /etc/frameworkd.conf if it 
isn't enabled already. After restarting frameworkd (reboot is easiest) you 
should be able to see debug output using logread -f.

It may be worth checking the thread "[SHR] GPRS / FATAL: Error inserting 
ppp_mppe" on the community list as it seems to be covering similar ground.

What's this about an extra number that you need to enter? Is there a 
documentation page you can point us to?

> I downloaded a copy of fso-config-util.py, I am uncertain if there is
> an official version of it.

http://openmoko.truebox.co.uk/tools/fso/fso-config-util.py

Unless someone's made an updated version I don't know about ;-)

> Is there an official howto for SHR?  Has anyone gotten to work with AT&T?
>
> Thanks
>
> On Mon, Dec 15, 2008 at 2:36 PM, D. Gassen  wrote:
> > Hm, I'm on FSO (somewhat close to FSO, I'm a bit scared to update ;-))
> > but I get the same error message in the logs. However, gprs works fine
> > with me (T-Mobile, USA).
> >
> > Have you checked if GPRS is working despite this error message?
> >
> > Dirk
> >
> > On 15.12.2008, at 14:16, Paul wrote:
> >> I know there are reports that GPRS does work with SHR.
> >>
> >> I've download the fso-config-util.py script and edited my apn
> >> settings, although for cingular/at&t, there is another number its
> >> supposed to dial but no place to put it in the script.  When I hit
> >> connect, it just says, release.
> >>
> >> Any advice?
> >>
> >> Thanks in advance.
> >> --
> >> Paul
> >> Email - pault...@gmail.com
> >>
> >> There were moments when he looked on evil simply as a mode through
> >> which he could realize his conception of the beautiful.
> >> Oscar Wilde - The Picture of Dorian Gray
> >>
> >> ___
> >> support mailing list
> >> support@lists.openmoko.org
> >> https://lists.openmoko.org/mailman/listinfo/support
> >
> > ___
> > support mailing list
> > support@lists.openmoko.org
> > https://lists.openmoko.org/mailman/listinfo/support



___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: /etc/init.d/fso-gpsd pid-file off by one

[Sascha Wessel]

Hi,

On Tue, Dec 16, 2008 at 01:21:43AM +0100, Joachim Ott wrote:
> 2008/12/15 Sascha Wessel 
> > On Mon, Dec 15, 2008 at 04:28:45PM +0100, Joachim Ott wrote:
> > > Could it be that the PID-file is written before the fork() rather than
> > after
> > > it?
> >
> > fso-gpsd forks itself to the background.
> 
> 
> That's what I wrote. The fucking PID-file is written before the fucking fork
> is made.

not if fso-gpsd writes the pid file

> > > created and a simple "killall -q fso-gpsd" is sufficient to terminate it.
> >
> > > Anyway, there can be only one fso-gpsd running, no PID-file needs to be
> >
> > There can be more than one.
> >
> 
> Wrong. There can be only 1 fucking (in words:ONE  FUCKING) process that
> binds to port 2947.

use another port


Greetings,
Sascha


___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: /etc/init.d/fso-gpsd pid-file off by one

[Michael 'Mickey' Lauer]

Excuse me, you're surely trying to make a point here, but I could not follow 
because I was distracted by your unnecessary use of rude language.

Please try to avoid that next time.

-- 
:M:

___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: /etc/init.d/fso-gpsd pid-file off by one

[Joachim Ott]

2008/12/15 Sascha Wessel 

> On Mon, Dec 15, 2008 at 04:28:45PM +0100, Joachim Ott wrote:
> > Could it be that the PID-file is written before the fork() rather than
> after
> > it?
>
> fso-gpsd forks itself to the background.


That's what I wrote. The fucking PID-file is written before the fucking fork
is made.


> > created and a simple "killall -q fso-gpsd" is sufficient to terminate it.
>
> > Anyway, there can be only one fso-gpsd running, no PID-file needs to be
>
> There can be more than one.
>

Wrong. There can be only 1 fucking (in words:ONE  FUCKING) process that
binds to port 2947.
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: Sad Story

[The Rasterman]

On Tue, 16 Dec 2008 02:21:55 +0530 Karthik Kumar 
babbled:

> Al Johnson wrote:
> > Neither are representatives of Openmoko. They have bought phones just as
> > you and I have. I suspect that they are frustrated by this long and
> > unproductive thread, and by your perceived attitude. You don't appear to be
> > interested in getting solutions to whatever problems you may be having.
> > Suggesting someone is lying when they try to correct your misunderstanding
> > is just plain offencive where I come from, as are your unsubstantiated
> > accusations about Openmoko and their staff. This may simply be a cultural
> > misunderstanding, as is often the case on international lists, in which
> > case I suggest you correct it now.
> 
> See, I do understand that they've got their own pressures. But by merely
> trying to work on GTA03 (hardware or software), it's like they've thrown

i think here you have the reality of producing a device wrong. let me put this
straight. i used to work at openmoko. but i do not speak for them. openmoko
employs a group of people. some of them do hardware, some software. the
hardware goes do not know software or how to fix the higher level stuff - do
you expect them to sit idle and do NOTHING (not work on gta03) and get paid for
twiddling thumbs just because you are unhappy with the gta02? hell no. reality
is that they march on to do gta03. some of software implicitly marches on too.
openmoko is paying people to work on gta02 SOFTWARE and fix things. they spend
their days doing it. they can do little to FIX hardware you have as it's in
your hands. they CAN fix software as you can trivially download/flash updates.
i am not addressing ANYTHING ELSE you have said - i'm leaving it well alone. i
am ONLY addressing the work on GTA03 - they HAVE to do it. it's a reality of
business because they have a hardware division that otherwise sits idle.

-- 
- Codito, ergo sum - "I code, therefore I am" --
The Rasterman (Carsten Haitzler)ras...@rasterman.com


___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: Sad Story

[Ali]

On Tue, 2008-12-16 at 02:21 +0530, Karthik Kumar wrote:
> See, I do understand that they've got their own pressures. But by merely
> trying to work on GTA03 (hardware or software), it's like they've thrown
> their hands off the GTA02. And that's not the right attitude towards
> that either. I hope that this thread at least awakens them to the
> reality that their users are frustrated with them not doing anything
> over the GTA02. ..

I have been following this thread for a while and I'm fairly sure it's
been explained to you very specifically (and even if not, there have
been at least a few posts about this): when they said they were working
on gta03 they meant the software stack that will be default for the
gta03 hardware. This means the old gta02 will still work with the new
software, they are just calling the new one gta03 internally/by
mistake/whatever. No  one is abandoning gta02, there have never been any
plans mentioned on the list to do so (not by any openmoko rep anyway),
the focus has just changed to a stack that will work even better (FSO if
you were wondering). The reason some people are getting pissed at you
(and telling you to go buy an iphone) is because people have explained
almost all of your complaints, in great detail, and until recently you
did not seem to comprehend that. Criticism is good, very good, but if
and only if it is constructive- that is key. If you complain about
something that is already being worked on or that already has been fixed
that is not constructive. Also remember that this is a public list in
that anyone can post on here, not just representatives of openmoko,
though they can and do as well. I'm going to provide you a list of
places you should search and look through before complaining things do
not work.

The wiki: http://wiki.openmoko.org/wiki/Main_Page -start here, enter
queries into the search bar, lots of info
The mailing lists: http://lists.openmoko.org/mailman/listinfo/ -some
posts have s much info on specific problems- but seeing as how you
are posting here I'm sure you knew of those.
The bug tacker: http://docs.openmoko.org/trac/ -here you will see if and
when specific problems have been reported, when they will get fixed, and
you can even report bugs there (i would strongly recommended reading
through http://wiki.openmoko.org/wiki/Bug_Filing_Policy it will give you
all the detail you need to filing a good *constructive* bug report).  
A good kernel (I haven't tried it myself but i've heard good things
about it): http://people.openmoko.org/andy/ 
The kernel I use (though a touch dated now, still not bad):
http://moko.mwester.net/ 

If you have not seen this already, I think you might enjoy it quite a
bit: http://wiki.openmoko.org/wiki/Jokes 

Last but not least, if you want a working phone above all else-
incidentally what I also require- http://other.lastnetwork.net/OpenMoko/
has some supposedly good qt extended images. Use in combo with Andy
tracking and if that does not work mwester's kernel is good.
http://wiki.openmoko.org/wiki/Distributions - a detailed list of
distro's

 To be clear, complain if there is a genuine problem- that is good, but
check other places first to make sure it has not been acknowledged.
(while i'm venting) One other thing I noticed about the thread that
bothered me, someone had said something to the effect of: this thread
would not exist if there were no problems, therefor the problems must
exist. Please see http://en.wikipedia.org/wiki/Begging_the_question a
very common logical fallacy.
There are many things one can do with a freerunner, even with the
constant changes that go on, I hope you find a combo of software that
works for you and your needs. 



___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: Sad Story

[Dale Maggee]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Karthik Kumar wrote:
>> I know better.

I could debate that at great length, cuz it's pretty god damn obvious to
us all that you don't know shit, but I've had a better Idea - I'm just
gonna create a filter to automatically delete anything sent by you. I
hope for your sake you never have a problem with NeoTool.

bye now.

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFJRt2TFbVnQRV3OEYRAo7nAJ0aoKsVyqebSdK2YfULPBq2YUKejwCfdm2d
47HxhLbTnMGK2mTAIlacvkQ=
=ttHp
-END PGP SIGNATURE-

___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: Sad Story

[Juan Cañete]

Hi all, 

I'm quite impressed and dissapointed about what the mail I sent has caused. I 
could have not imagine it...I'm sorry.

I would like to say what I think, trying not to reply or offend anyone so, 
please we can stop with this thread now, or at least this is my last mail.

Open source is a matter of work, patience and hopes. When we bought an OM 
mobile, we knew that it was on the cutting edge of GPL mobile software 
technology. We could have a linux box in our pocket, integrating a music 
player, mobile phone, computer, etc, all in one. We were excited about all the 
posibilities it could have, and We wanted it to work well and now. But things 
are not so easy: design HW errors, difficulties in kernel development, problems 
with UI integration... As a result, we blame on the neighbour of all this, but 
that, in my opinion, is not they way to follow, every one has his part of 
responsibility. Everybody of us could help more instead of creating a feeling 
of tension in the air.

It's true there are HW problems, maybe they will never get fixed in software 
and they'll need a HW repair, but this is an OM matter, and their decision will 
be important in future purchases of us. Soon or later all the work that is 
being made here by the community will be taken in advantage by others mobile 
manufacturers. It's a matter of OM to design good mobile phones if they want to 
be chosen by us in the near future. I'm sure they are putting their best 
efforts on it.

Some of us are dissapointed with the actual OM mobile phones. This phones are 
pioneers, it's sad to say, but it's all what we get by now. So, if someone has 
no patience, no hopes and don't want to help us in this, I would advise him to 
sell the phone. Working on something without entusiasm will age you sooner. For 
all of you who hope some day to pick up your phone in a lift full of people and 
that the phone has battery on it or it doen't show de WSOD or whatever, stay 
here and try to help everybody in making better our phone. Everyone here, OM, 
kernel developers, etc, see the problems, but they don't need us to blame them, 
all they need of us is hopes, patience and work, no more.

best regards.

 
 
-- 
Juan Cañete Azorín
hiroshima 45, Tchernobyl 86, Windows 95 ...
Powered by Linux



signature.asc
Description: PGP signature
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: Sad Story

[Sargun Dhillon]

Battery decay is not linear.

On Mon, Dec 15, 2008 at 2:18 PM, Timo Juhani Lindfors
 wrote:
> Stefan Monnier  writes:
>> - unreliable suspend (supposedly fixed in upcoming kernels)
>
> Yes, I have used stable-tracking 80f4b57fef now for 15 days and resume
> works as long as I have use "sleep 4; apm -s; sleep 4" to suspend
> (there is some race somewhere but this avoids it).
>
>> - constant re-registration (here as well, there's a software
>>   workaround, which apparently causes a minor reduction in autonomy, tho
>>   it's not clear yet how minor: it depends on how well suspend works for 
>> you).
>
> Here I lose about 3.6 percentage units per hour. If the units are
> linear that means 100/3.6 = 28 hours of suspend time. This is enough
> for me since I can charge the phone over night.
>
> I also bought external USB battery for $14 from
> http://www.dealextreme.com/details.dx/sku.3060 which I use when I am
> away from home for more than one day.
>
> ___
> support mailing list
> support@lists.openmoko.org
> https://lists.openmoko.org/mailman/listinfo/support
>

___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: Sad Story

[Timo Juhani Lindfors]

Stefan Monnier  writes:
> - unreliable suspend (supposedly fixed in upcoming kernels)

Yes, I have used stable-tracking 80f4b57fef now for 15 days and resume
works as long as I have use "sleep 4; apm -s; sleep 4" to suspend
(there is some race somewhere but this avoids it).

> - constant re-registration (here as well, there's a software
>   workaround, which apparently causes a minor reduction in autonomy, tho
>   it's not clear yet how minor: it depends on how well suspend works for you).

Here I lose about 3.6 percentage units per hour. If the units are
linear that means 100/3.6 = 28 hours of suspend time. This is enough
for me since I can charge the phone over night.

I also bought external USB battery for $14 from
http://www.dealextreme.com/details.dx/sku.3060 which I use when I am
away from home for more than one day.

___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: Sad Story

[Kosa]

Karthik Kumar escribió:

  What were they doing before this thread then? 

They were working as hard as they can, perhaps even harder. Me and many
others
have seen that, sorry you can't, but you will.

  Were they productive at
all? If they were, this thread wouldn't exist. 

This thread exists becouse some bulgars stole Juan Cañate's FR,
remember? That is why
the subject was "sad story" in the first place. But eventhough it _is_
a sad story, you have
make it much more sad.

  And, if they wanted to
be productive, using this thread would be their worst excuse to do
something.

If they deliver, I'll stop talking on this thread.
  

Andy asked you to do it before, but I do +1 on it. You just fork this
senseless thread and 
ask for specific things. You don't go with "I want it to work right
know", please.

Kosa

- Un mundo mejor es posible -

  On Mon, Dec 15, 2008 at 9:12 PM, Al Johnson
 wrote:
  
  
Neither are representatives of Openmoko. They have bought phones just as you
and I have. I suspect that they are frustrated by this long and unproductive
thread, and by your perceived attitude. You don't appear to be interested in
getting solutions to whatever problems you may be having. Suggesting someone
is lying when they try to correct your misunderstanding is just plain
offencive where I come from, as are your unsubstantiated accusations about
Openmoko and their staff. This may simply be a cultural misunderstanding, as
is often the case on international lists, in which case I suggest you correct
it now.

On Monday 15 December 2008, Karthik Kumar wrote:


  Is that how you reply as a company which makes a phone? We can't fix
it so go buy our competitors' closed phones? I'd expect better from
you (like saying, yes, we'll fix it) than buy our competitor's phone.
If i had bought the competitors' phone, i wouldn't be cribbing now
that i've bought your phone, right?

Maybe Openmoko should trade in iPhones instead of Freerunners,
considering I already paid for a Freerunner. What do you think for
that for a response?

On Mon, Dec 15, 2008 at 4:44 PM, arne anka  wrote:
  
  

  Karthik:

I think I probably speak for a reasonable portion of the community when
I say this:

Go buy an iphone. Put your FreeRunner on ebay. You'll like the iphone -
  

+1

___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

  
  ___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support
  



___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support


  
  


  




___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: Sad Story

[Karthik Kumar]

Al Johnson wrote:
> Neither are representatives of Openmoko. They have bought phones just as you 
> and I have. I suspect that they are frustrated by this long and unproductive 
> thread, and by your perceived attitude. You don't appear to be interested in 
> getting solutions to whatever problems you may be having. Suggesting someone 
> is lying when they try to correct your misunderstanding is just plain 
> offencive where I come from, as are your unsubstantiated accusations about 
> Openmoko and their staff. This may simply be a cultural misunderstanding, as 
> is often the case on international lists, in which case I suggest you correct 
> it now.
>   

See, I do understand that they've got their own pressures. But by merely
trying to work on GTA03 (hardware or software), it's like they've thrown
their hands off the GTA02. And that's not the right attitude towards
that either. I hope that this thread at least awakens them to the
reality that their users are frustrated with them not doing anything
over the GTA02. If they did sort out ALL major issues (kernel, GSM
firmware, u-boot, major device userland daemons) then they could at
least feel better about themselves. But simply switching to work on
GTA03 is to piss on the community which has funded you till now. I hope
they take this up seriously than treat it as a discouragement or dismiss
it as a whiny joke :P
> On Monday 15 December 2008, Karthik Kumar wrote:
>   
>> Is that how you reply as a company which makes a phone? We can't fix
>> it so go buy our competitors' closed phones? I'd expect better from
>> you (like saying, yes, we'll fix it) than buy our competitor's phone.
>> If i had bought the competitors' phone, i wouldn't be cribbing now
>> that i've bought your phone, right?
>>
>> Maybe Openmoko should trade in iPhones instead of Freerunners,
>> considering I already paid for a Freerunner. What do you think for
>> that for a response?
>>
>> On Mon, Dec 15, 2008 at 4:44 PM, arne anka  wrote:
>> 
 Karthik:

 I think I probably speak for a reasonable portion of the community when
 I say this:

 Go buy an iphone. Put your FreeRunner on ebay. You'll like the iphone -
 
>>> +1
>>>
>>> ___
>>> support mailing list
>>> support@lists.openmoko.org
>>> https://lists.openmoko.org/mailman/listinfo/support
>>>   
>> ___
>> support mailing list
>> support@lists.openmoko.org
>> https://lists.openmoko.org/mailman/listinfo/support
>> 
>
>
>
> ___
> support mailing list
> support@lists.openmoko.org
> https://lists.openmoko.org/mailman/listinfo/support
>
>   


___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: Sad Story

[Karthik Kumar]

Okay, Al. That's one of the most sensible replies on this thread; I hear
ya. I'll dig deeper into this.

Al Johnson wrote:
> On Monday 15 December 2008, Karthik Kumar wrote:
>   
>> On Mon, Dec 15, 2008 at 5:35 AM, Stefan Monnier
>>
>>  wrote:
>> 
>> There are still hardware problems that exist with almost every
>> freerunner out there (GPS signal levels, for one).  I would like to
>> see them fixed by Openmoko, Inc.
>> 
 The kernel fix for GPS is a mere quirk. Ideally it should get fixed in
 hardware.
 
>>> Huh?  The kernel fix seems to work OK for those people who have old
>>> FRs.  Newer FRs have a hardware fix.  E.g. my FR doesn't need any
>>> kernel workaround.  No need to wait for GTA03 to get a hardware fix.
>>>   
>> So, this kernel fix is a feature, according to Al Johnson? Then why do
>> they need a hardware fix?
>> 
>
> They don't. Neither of my Freerunners has the hardware fix, and the GPS works 
> just fine with any kernel that includes the fix.
>
>   
>> Unless I am missing something, this software  
>> fix seems to be a lie. Or the hardware fix seems to be bogus anyway.
>> 
>
> You are missing something, so I will try to explain. The 'hardware fix' is a 
> small capacitor from the SD clock line to ground, and was a quick response to 
> the problem when the SD was discovered to be interfering with the GPS. This 
> slows the transition between the digital high and low states, reducing the 
> level of interference generated. Reducing the drive strength does the same 
> thing, but through a slightly different mechanism, and doesn't require a 
> soldering iron to make the change. Note that the hardware fix only reduces 
> interference from the clock line. The kernel fix reduces interference from 
> the other signal lines too.
>
> To understand the issues more fully I suggest you read up on the analogue 
> properties of digital electronics, particularly in regard to the speed of 
> transitions and their effect on EMI.
>
>   
>> I have one of the earlier freerunners released, so I'm sure Openmoko
>> owes an explanation.
>> 
>
> Both hardware and software fixes were discussed extensively on the lists, and 
> are in the list archive. 
>
> ___
> support mailing list
> support@lists.openmoko.org
> https://lists.openmoko.org/mailman/listinfo/support
>
>   


___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: Sad Story

[Stefan Monnier]

> So, this kernel fix is a feature, according to Al Johnson? Then why do
> they need a hardware fix? Unless I am missing something, this software
> fix seems to be a lie.  Or the hardware fix seems to be bogus anyway.
> I have one of the earlier freerunners released, so I'm sure Openmoko
> owes an explanation.

I do not know.  I simply know that the FR I got a few months ago has
a fully functional GPS: works just as well as any other GPS around.
Also, for those people who had an earlier FR, there is a software
workaround that apparently makes it work almost as good as well.

I'm not sure what more do you expect.  To recapitulate, you said:
> There are still hardware problems that exist with almost every
> freerunner out there (GPS signal levels, for one).  I would like to
> see them fixed by Openmoko, Inc.

AFAIK, the problems of GPS signal level only affect a fairly small
proportion of the FRs out there, and they have been fixed by Openmoko.

There are plenty of real problems left, that I don't see why we should
bring this GPS problem back from the dead.  Of the real problems:
- unreliable suspend (supposedly fixed in upcoming kernels)
- echo (there's supposedly a software workaround, but it basically puts
  the phone in a sort of half-duplex mode, so it's not perfect).
- buzz.
- constant re-registration (here as well, there's a software
  workaround, which apparently causes a minor reduction in autonomy, tho
  it's not clear yet how minor: it depends on how well suspend works for you).
- the audio line-out is unusable to listen to music because of a poorly
  chosen capacitor that cuts off low-frequencies.
- the wifi antenna apparently stays on even while you suspend,
  reducing autonomy.
- wifi with WPA has trouble switching to some other networks
  (apparently someone is working on this or may even have found the bug
  already).
- ...


Stefan


___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: Sad Story

[Karthik Kumar]

What were they doing before this thread then? Were they productive at
all? If they were, this thread wouldn't exist. And, if they wanted to
be productive, using this thread would be their worst excuse to do
something.

If they deliver, I'll stop talking on this thread.

On Mon, Dec 15, 2008 at 9:12 PM, Al Johnson
 wrote:
> Neither are representatives of Openmoko. They have bought phones just as you
> and I have. I suspect that they are frustrated by this long and unproductive
> thread, and by your perceived attitude. You don't appear to be interested in
> getting solutions to whatever problems you may be having. Suggesting someone
> is lying when they try to correct your misunderstanding is just plain
> offencive where I come from, as are your unsubstantiated accusations about
> Openmoko and their staff. This may simply be a cultural misunderstanding, as
> is often the case on international lists, in which case I suggest you correct
> it now.
>
> On Monday 15 December 2008, Karthik Kumar wrote:
>> Is that how you reply as a company which makes a phone? We can't fix
>> it so go buy our competitors' closed phones? I'd expect better from
>> you (like saying, yes, we'll fix it) than buy our competitor's phone.
>> If i had bought the competitors' phone, i wouldn't be cribbing now
>> that i've bought your phone, right?
>>
>> Maybe Openmoko should trade in iPhones instead of Freerunners,
>> considering I already paid for a Freerunner. What do you think for
>> that for a response?
>>
>> On Mon, Dec 15, 2008 at 4:44 PM, arne anka  wrote:
>> >> Karthik:
>> >>
>> >> I think I probably speak for a reasonable portion of the community when
>> >> I say this:
>> >>
>> >> Go buy an iphone. Put your FreeRunner on ebay. You'll like the iphone -
>> >
>> > +1
>> >
>> > ___
>> > support mailing list
>> > support@lists.openmoko.org
>> > https://lists.openmoko.org/mailman/listinfo/support
>>
>> ___
>> support mailing list
>> support@lists.openmoko.org
>> https://lists.openmoko.org/mailman/listinfo/support
>
>
>
> ___
> support mailing list
> support@lists.openmoko.org
> https://lists.openmoko.org/mailman/listinfo/support
>



-- 
Karthik
http://guilt.bafsoft.net

___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: Sad Story

[Karthik Kumar]

On Mon, Dec 15, 2008 at 6:50 PM, Dale Maggee  wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Karthik Kumar wrote:
>> Is that how you reply as a company which makes a phone? We can't fix
>> it so go buy our competitors' closed phones? I'd expect better from
>> you (like saying, yes, we'll fix it) than buy our competitor's phone.
>
> Um... when did openmoko say anything of the sort? Am I an OM employee
> but I just don't know it? you've just demonstrated yourself to be even
> stupider than I thought, which I must admit is quite an accomplishment,
> congratulations.

So you're not from Openmoko? Piss off, b*tch, You don't need to tell
me what I should do, I know better.

>
> No, really, go buy an iphone - they're designed for morons. You'll fit
> right in.
>
>> If i had bought the competitors' phone, i wouldn't be cribbing now
>> that i've bought your phone, right?
>
> No, you'd be languishing in an idiot's paradise, making phone calls and
> not bitching constantly... ok, so maybe that's premature, I'm sure you'd
> find something to bitch about... it's just that then you'd have to bitch
> to apple, and not us, and since apple don't care once they've got your
> money and can send automated responses, and we wouldn't have to put up
> with you anymore, it's really just a better arrangement for everybody.
>
>> Maybe Openmoko should trade in iPhones instead of Freerunners,
>> considering I already paid for a Freerunner. What do you think for
>> that for a response?
>
> What do I think of that for a response? Stupid and uninformed. What a
> big suprise.
>
> If it's really that bad, put your FR on ebay and go buy an iphone.
> everybody will be happier - not just you, but the thousands of poor sods
> like me who's inboxes are being clogged up on a daily basis with your
> bullshit.
>
> fsck off and go buy an iphone. Seriously.
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.7 (GNU/Linux)
> Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
>
> iD8DBQFJRlmfFbVnQRV3OEYRAoE7AJwIPDdrPxY6ImZFShtQXfXiWQR3ZgCgq1/a
> tXOJSTJI3Chncho4eKlIvUI=
> =T4w/
> -END PGP SIGNATURE-
>
> ___
> support mailing list
> support@lists.openmoko.org
> https://lists.openmoko.org/mailman/listinfo/support
>



-- 
Karthik
http://guilt.bafsoft.net

___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: SHR - GPRS

[Nathan Kinkade]

2008/12/15 Paul :
> Thank you for your response.
>
> I honestly do not know where to begin.  I am not receiving an error,
> it's just not connecting.  I did try the internet and it is not
> connecting.
>
> I downloaded a copy of fso-config-util.py, I am uncertain if there is
> an official version of it.
>
> Is there an official howto for SHR?  Has anyone gotten to work with AT&T?
>
> Thanks

Yes, I have GPRS working fine in SHR with AT&T.  It was very helpful
for me to do the following before I started GPRS:

# logread -f

pppd logs there and you'll likely see lots of relevant messages, maybe
even an obvious error.  As someone else pointed out, you've got to
make sure the ppp device exists in /dev which has been a problem on
SHR.  You can do it permanently via their instructions, or with:

# modprobe ppp_generic

I also made another simple graphical utility to launch GPRS.  See my post here:

http://lists.openmoko.org/nabble.html#nabble-td1655100

Nathan

___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: SHR - GPRS

[ZS-Man]

Hi, I tested new SHR image and GPRS works. Only ppp-generic module I must add
to autostart.

echo ppp-generic > /etc/modutils/ppp-generic
update-modules


ZS-Man


Paul-10 wrote:
> 
> I know there are reports that GPRS does work with SHR.
> 
> I've download the fso-config-util.py script and edited my apn
> settings, although for cingular/at&t, there is another number its
> supposed to dial but no place to put it in the script.  When I hit
> connect, it just says, release.
> 
> Any advice?
> 
> Thanks in advance.
> -- 
> Paul
> Email - pault...@gmail.com
> 
> There were moments when he looked on evil simply as a mode through
> which he could realize his conception of the beautiful.
> Oscar Wilde - The Picture of Dorian Gray
> 
> ___
> support mailing list
> support@lists.openmoko.org
> https://lists.openmoko.org/mailman/listinfo/support
> 

-- 
View this message in context: 
http://n2.nabble.com/SHR---GPRS-tp1659546p1659717.html
Sent from the Openmoko Support mailing list archive at Nabble.com.


___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: SHR - GPRS

[Paul]

Thank you for your response.

I honestly do not know where to begin.  I am not receiving an error,
it's just not connecting.  I did try the internet and it is not
connecting.

I downloaded a copy of fso-config-util.py, I am uncertain if there is
an official version of it.

Is there an official howto for SHR?  Has anyone gotten to work with AT&T?

Thanks

On Mon, Dec 15, 2008 at 2:36 PM, D. Gassen  wrote:
> Hm, I'm on FSO (somewhat close to FSO, I'm a bit scared to update ;-))
> but I get the same error message in the logs. However, gprs works fine
> with me (T-Mobile, USA).
>
> Have you checked if GPRS is working despite this error message?
>
> Dirk
>
> On 15.12.2008, at 14:16, Paul wrote:
>
>> I know there are reports that GPRS does work with SHR.
>>
>> I've download the fso-config-util.py script and edited my apn
>> settings, although for cingular/at&t, there is another number its
>> supposed to dial but no place to put it in the script.  When I hit
>> connect, it just says, release.
>>
>> Any advice?
>>
>> Thanks in advance.
>> --
>> Paul
>> Email - pault...@gmail.com
>>
>> There were moments when he looked on evil simply as a mode through
>> which he could realize his conception of the beautiful.
>> Oscar Wilde - The Picture of Dorian Gray
>>
>> ___
>> support mailing list
>> support@lists.openmoko.org
>> https://lists.openmoko.org/mailman/listinfo/support
>
>
> ___
> support mailing list
> support@lists.openmoko.org
> https://lists.openmoko.org/mailman/listinfo/support
>



-- 
Paul
Email - pault...@gmail.com

There were moments when he looked on evil simply as a mode through
which he could realize his conception of the beautiful.
Oscar Wilde - The Picture of Dorian Gray

___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: Sad Story

[Paul]

Seeing the responses to criticism, it is clear why OpenMoko is where
it is today.  If a significant portion of the community is frustrated
at the status of this project, the best course of action is to address
the concerns of the community.  Does telling people to buy an iphone
accomplish anything but lower your social standing on this list?

The main reason of why Open Source works is because people are able to
criticize.  When the criticisms are taken into account, real progress
can be had.

We as a community were warned of the alpha status of the phone.  What
we expected was that the community and company would work hand in hand
to create a viable phone solution.  Yet, it is clear that the resolve
of the Company is waning and the rest of the community is left holding
the bag.  Now we have people blaming us because we are holding the
bag.

Just because a project is Open Source, doesn't guarantee its success.
We have a lot of people working hard to resolve issues, yet we haven't
achieved our goal.  We need to refocus our goals and objectives to
create a working phone.  Passing the buck to FSO is passing the torch
to someone else.  This is what OM has done.

I'm sure the majority of hardware owners are awaiting Google Android.
-- 
Paul
Email - pault...@gmail.com

There were moments when he looked on evil simply as a mode through
which he could realize his conception of the beautiful.
Oscar Wilde - The Picture of Dorian Gray

___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: SHR - GPRS

[Michael 'Mickey' Lauer]

Am Monday 15 December 2008 20:16:14 schrieb Paul:
> I know there are reports that GPRS does work with SHR.
>
> I've download the fso-config-util.py script and edited my apn
> settings, although for cingular/at&t, there is another number its
> supposed to dial but no place to put it in the script.  When I hit
> connect, it just says, release.

Please send us a debug log.

-- 
:M:

___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: SHR - GPRS

[D. Gassen]

Hm, I'm on FSO (somewhat close to FSO, I'm a bit scared to update ;-))  
but I get the same error message in the logs. However, gprs works fine  
with me (T-Mobile, USA).

Have you checked if GPRS is working despite this error message?

Dirk

On 15.12.2008, at 14:16, Paul wrote:

> I know there are reports that GPRS does work with SHR.
>
> I've download the fso-config-util.py script and edited my apn
> settings, although for cingular/at&t, there is another number its
> supposed to dial but no place to put it in the script.  When I hit
> connect, it just says, release.
>
> Any advice?
>
> Thanks in advance.
> -- 
> Paul
> Email - pault...@gmail.com
>
> There were moments when he looked on evil simply as a mode through
> which he could realize his conception of the beautiful.
> Oscar Wilde - The Picture of Dorian Gray
>
> ___
> support mailing list
> support@lists.openmoko.org
> https://lists.openmoko.org/mailman/listinfo/support


___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

SHR - GPRS

[Paul]

I know there are reports that GPRS does work with SHR.

I've download the fso-config-util.py script and edited my apn
settings, although for cingular/at&t, there is another number its
supposed to dial but no place to put it in the script.  When I hit
connect, it just says, release.

Any advice?

Thanks in advance.
-- 
Paul
Email - pault...@gmail.com

There were moments when he looked on evil simply as a mode through
which he could realize his conception of the beautiful.
Oscar Wilde - The Picture of Dorian Gray

___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: Other possible Echo Cause

[Al Johnson]

On Monday 15 December 2008, Paul wrote:
> > It's possible, but the buzz is within the voice frequency range. If we
> > could characterise the buzz sufficiently it may be possible to remove it
> > by applying a suitable digital filter in the CPU, but a hardware fix is
> > certainly preferable.
>
> I was thinking a software noise gate would be preferable since it
> requires less computing.  Also, anyone tried sound proofing the mic
> with sound insulating foam to prevent the sound from traveling through
> the phone?

There's a noise gate in the Wolfson chip, but I never managed to get it 
working. The functions in the GSM chipset sound like a noise gate in 
operation too. A better low-computing method might be to monitor the GSM 
output and mute the mic if there is significant signal there. This approach 
is used by some VoIP handsets ad is very effective at preventing echo, but 
can be awkward as the other end can't hear when you interrupt them ;-)

The mic has rubber around it which seals the gap between the mic and the case. 
I haven't tried modifying this.

___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: Other possible Echo Cause

[Paul]

> If you mute either the mic or the earpiece there is no echo. If you use the
> wired headset there is no echo. The level of echo is affected by both the mic
> gain and the earpiece level. Using the speakerphone gives much more echo,
> which is expected because the volume is higher and the speaker is close to
> the mic.

Thank you for confirming this.

> It's possible, but the buzz is within the voice frequency range. If we could
> characterise the buzz sufficiently it may be possible to remove it by
> applying a suitable digital filter in the CPU, but a hardware fix is
> certainly preferable.

I was thinking a software noise gate would be preferable since it
requires less computing.  Also, anyone tried sound proofing the mic
with sound insulating foam to prevent the sound from traveling through
the phone?

-- 
Paul
Email - pault...@gmail.com

There were moments when he looked on evil simply as a mode through
which he could realize his conception of the beautiful.
Oscar Wilde - The Picture of Dorian Gray

___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: /etc/init.d/fso-gpsd pid-file off by one

[Sascha Wessel]

Hi,


On Mon, Dec 15, 2008 at 04:28:45PM +0100, Joachim Ott wrote:
> Could it be that the PID-file is written before the fork() rather than after
> it?

fso-gpsd forks itself to the background.

> Anyway, there can be only one fso-gpsd running, no PID-file needs to be
> created and a simple "killall -q fso-gpsd" is sufficient to terminate it.

There can be more than one.

For a working example, see [1] or [2].


Greetings,
Sascha


http://git.freesmartphone.org/?p=fso-gpsd.git;a=blob;f=init-fso-gpsd
http://git.debian.org/?p=pkg-fso/fso-gpsd.git;a=blob;f=debian/fso-gpsd.init


___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: Sad Story

[Al Johnson]

Neither are representatives of Openmoko. They have bought phones just as you 
and I have. I suspect that they are frustrated by this long and unproductive 
thread, and by your perceived attitude. You don't appear to be interested in 
getting solutions to whatever problems you may be having. Suggesting someone 
is lying when they try to correct your misunderstanding is just plain 
offencive where I come from, as are your unsubstantiated accusations about 
Openmoko and their staff. This may simply be a cultural misunderstanding, as 
is often the case on international lists, in which case I suggest you correct 
it now.

On Monday 15 December 2008, Karthik Kumar wrote:
> Is that how you reply as a company which makes a phone? We can't fix
> it so go buy our competitors' closed phones? I'd expect better from
> you (like saying, yes, we'll fix it) than buy our competitor's phone.
> If i had bought the competitors' phone, i wouldn't be cribbing now
> that i've bought your phone, right?
>
> Maybe Openmoko should trade in iPhones instead of Freerunners,
> considering I already paid for a Freerunner. What do you think for
> that for a response?
>
> On Mon, Dec 15, 2008 at 4:44 PM, arne anka  wrote:
> >> Karthik:
> >>
> >> I think I probably speak for a reasonable portion of the community when
> >> I say this:
> >>
> >> Go buy an iphone. Put your FreeRunner on ebay. You'll like the iphone -
> >
> > +1
> >
> > ___
> > support mailing list
> > support@lists.openmoko.org
> > https://lists.openmoko.org/mailman/listinfo/support
>
> ___
> support mailing list
> support@lists.openmoko.org
> https://lists.openmoko.org/mailman/listinfo/support



___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

/etc/init.d/fso-gpsd pid-file off by one

[Joachim Ott]

Could it be that the PID-file is written before the fork() rather than after
it? Anyway, there can be only one fso-gpsd running, no PID-file needs to be
created and a simple "killall -q fso-gpsd" is sufficient to terminate it.
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: Sad Story

[Al Johnson]

On Monday 15 December 2008, Karthik Kumar wrote:
> On Mon, Dec 15, 2008 at 5:35 AM, Stefan Monnier
>
>  wrote:
>  There are still hardware problems that exist with almost every
>  freerunner out there (GPS signal levels, for one).  I would like to
>  see them fixed by Openmoko, Inc.
> >>
> >> The kernel fix for GPS is a mere quirk. Ideally it should get fixed in
> >> hardware.
> >
> > Huh?  The kernel fix seems to work OK for those people who have old
> > FRs.  Newer FRs have a hardware fix.  E.g. my FR doesn't need any
> > kernel workaround.  No need to wait for GTA03 to get a hardware fix.
>
> So, this kernel fix is a feature, according to Al Johnson? Then why do
> they need a hardware fix?

They don't. Neither of my Freerunners has the hardware fix, and the GPS works 
just fine with any kernel that includes the fix.

> Unless I am missing something, this software  
> fix seems to be a lie. Or the hardware fix seems to be bogus anyway.

You are missing something, so I will try to explain. The 'hardware fix' is a 
small capacitor from the SD clock line to ground, and was a quick response to 
the problem when the SD was discovered to be interfering with the GPS. This 
slows the transition between the digital high and low states, reducing the 
level of interference generated. Reducing the drive strength does the same 
thing, but through a slightly different mechanism, and doesn't require a 
soldering iron to make the change. Note that the hardware fix only reduces 
interference from the clock line. The kernel fix reduces interference from 
the other signal lines too.

To understand the issues more fully I suggest you read up on the analogue 
properties of digital electronics, particularly in regard to the speed of 
transitions and their effect on EMI.

> I have one of the earlier freerunners released, so I'm sure Openmoko
> owes an explanation.

Both hardware and software fixes were discussed extensively on the lists, and 
are in the list archive. 

___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Stable Upgrade Anytime Soon?

[Marcus Stong]

It's been over a month now that opkg upgrade has produced nothing
whatsoever. I know the "back to basics" are being worked on, but does anyone
know how long until something makes it to the stable feed? I know part of my
frustration relating to me venting on the whole "sad story" thread has been
partially because it really seems like nothing is happening. I realize
there's a testing feed, but I don't really have the time to go through all
the steps to make it work for a while.

I don't see why it's taking so long to pass anything to the stable feed.
It's not like it's really stable to begin with, so there isn't much to lose.
The dialer crashes, suspend freezes, and there's low call volume using FDOM
or OM2008.9. I really would like to see a carrot dangled in front of my
nose... that's always been the fun with this phone, and there haven't been
too many carrots lately.

Marcus
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: Sad Story

[Dale Maggee]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Karthik Kumar wrote:
> Is that how you reply as a company which makes a phone? We can't fix
> it so go buy our competitors' closed phones? I'd expect better from
> you (like saying, yes, we'll fix it) than buy our competitor's phone.

Um... when did openmoko say anything of the sort? Am I an OM employee
but I just don't know it? you've just demonstrated yourself to be even
stupider than I thought, which I must admit is quite an accomplishment,
congratulations.

No, really, go buy an iphone - they're designed for morons. You'll fit
right in.

> If i had bought the competitors' phone, i wouldn't be cribbing now
> that i've bought your phone, right?

No, you'd be languishing in an idiot's paradise, making phone calls and
not bitching constantly... ok, so maybe that's premature, I'm sure you'd
find something to bitch about... it's just that then you'd have to bitch
to apple, and not us, and since apple don't care once they've got your
money and can send automated responses, and we wouldn't have to put up
with you anymore, it's really just a better arrangement for everybody.

> Maybe Openmoko should trade in iPhones instead of Freerunners,
> considering I already paid for a Freerunner. What do you think for
> that for a response?

What do I think of that for a response? Stupid and uninformed. What a
big suprise.

If it's really that bad, put your FR on ebay and go buy an iphone.
everybody will be happier - not just you, but the thousands of poor sods
like me who's inboxes are being clogged up on a daily basis with your
bullshit.

fsck off and go buy an iphone. Seriously.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFJRlmfFbVnQRV3OEYRAoE7AJwIPDdrPxY6ImZFShtQXfXiWQR3ZgCgq1/a
tXOJSTJI3Chncho4eKlIvUI=
=T4w/
-END PGP SIGNATURE-

___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: German layout for usb keyboard?

[Joachim Ott]

2008/12/15 Konstantin 

> Hi there!
>
> I just got my mini-usb-keyboard for my freerunner, and I'm very happy that
> it
> works "out of the box" - mostly, that is: How do I set a german layout for
> the
> keyboard under X? Normally, I would have done it by editing the xorg.conf,
> but
> since I can't find it, there has got to be another way, right?
> Any help would be very much appreciated :)


At least you can use xmodmap to change from default US to DE. Depending on
your distribution you might have other tools to change the layout.
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: Sad Story

[Karthik Kumar]

Is that how you reply as a company which makes a phone? We can't fix
it so go buy our competitors' closed phones? I'd expect better from
you (like saying, yes, we'll fix it) than buy our competitor's phone.
If i had bought the competitors' phone, i wouldn't be cribbing now
that i've bought your phone, right?

Maybe Openmoko should trade in iPhones instead of Freerunners,
considering I already paid for a Freerunner. What do you think for
that for a response?

On Mon, Dec 15, 2008 at 4:44 PM, arne anka  wrote:
>> Karthik:
>>
>> I think I probably speak for a reasonable portion of the community when
>> I say this:
>>
>> Go buy an iphone. Put your FreeRunner on ebay. You'll like the iphone -
>
> +1
>
> ___
> support mailing list
> support@lists.openmoko.org
> https://lists.openmoko.org/mailman/listinfo/support
>

___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: pointless ranting was: Re: Sad Story

[Karthik Kumar]

Arne, am I the only one paranoid here?

How do we know that you're not just lying about GTA03 being only plain
software. And, if you are, do we blame openmoko when it releases the
actual GTA03 board next year? And, if you're not, why don't you
instead fix the CURRENT GTA02 software?

;p

-Karthik

On Mon, Dec 15, 2008 at 4:34 PM, arne anka  wrote:
>>> if you refuse to check archives and to read mails and instead insist on
>>> perpetuating your misstatement, nobody can help you!
>>
>> Then this link be updated. http://wiki.openmoko.org/wiki/GTA03
>
>
> i give up.
> you are deliberatly confusing things just to prove your point, imo.
>
> eot for me.
>
> ___
> support mailing list
> support@lists.openmoko.org
> https://lists.openmoko.org/mailman/listinfo/support
>

___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: JFFS2 warning: (1157) jffs2_sum_write_sumnode: Not enough space for summary, padsize = -1212

[Joachim Ott]

2008/12/15 Nathan Kinkade 

> 2008/12/14 Joachim Ott :
> > I wonder what the 1157 means. Looking thru earlier logfiles, it happened
> > once for Dec 1, 3 and 4, 3 times for Dec 10, 5 times for Dec 14 and just
> > once some minutes ago for Dec 15. Needless to say that
> >
> > FilesystemSize  Used Available Use% Mounted on
> > rootfs  246.6M129.2M117.4M  52% /
> >
> > All this on SHR with Linux version 2.6.24 (s...@opmbuild) (gcc version
> 4.1.2)
> > #1 PREEMPT Sun Dec 14 18:55:25 CET 2008. Should I take any care of this?
>
> I'm using SHR as well and I noticed this same (or similar) error a day
> or two ago.  It just so happened that I was at that time watching the
> logs with logread, and when it happened the system froze, the screen
> went black and I had to take the battery out to revive it.  It's
> possible that those two events were unrelated.  Did you notice any
> problem when you saw that message, or did it seem to be benign?


This messages come up at boot time, usually 1 or 2 minutes after mounting
rootfs, like this:

Dec 15 03:17:32 (none) user.info kernel: pcf50633 0-0073: setting system
clock to 2008-12-15 02:16:58 UTC (1229307418)
Dec 15 03:17:32 (none) user.warn kernel: CRCFAIL 0x1a3f
Dec 15 03:17:32 (none) user.warn kernel: VFS: Mounted root (jffs2
filesystem).
Dec 15 03:17:32 (none) user.info kernel: Freeing init memory: 132K
Dec 15 03:17:32 (none) user.warn kernel: CRCFAIL 0x1a3f
--
Dec 15 03:17:47 (none) user.info gconfd (root-1214): Resolved address
"xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration
source at position 2
Dec 15 03:19:36 (none) user.warn kernel: ar6000_ioctl_giwscan(): data length
0
Dec 15 03:19:36 (none) user.warn kernel: JFFS2 warning: (1115)
jffs2_sum_write_sumnode: Not enough space for summary, padsize = -1122
Dec 15 03:19:39 (none) user.notice root: Checking for WLAN association...
Dec 15 03:19:39 (none) user.notice root: Found association!

or like this, took some minutes more:

Dec 15 03:41:57 om-gta02 user.info kernel: pcf50633 0-0073: setting system
clock to 2008-12-15 03:40:49 UTC (1229312449)
Dec 15 03:41:57 om-gta02 user.warn kernel: CRCFAIL 0x1a3f
Dec 15 03:41:57 om-gta02 user.warn kernel: VFS: Mounted root (jffs2
filesystem).
Dec 15 03:41:57 om-gta02 user.info kernel: Freeing init memory: 132K
Dec 15 03:41:57 om-gta02 user.warn kernel: CRCFAIL 0x1a3f
--
Dec 15 03:44:27 om-gta02 user.info kernel: jbt6k74 spi2.0:  jbt6k74
unblank
Dec 15 03:45:09 om-gta02 user.info kernel: jbt6k74 spi2.0:  jbt6k74
powerdown
Dec 15 03:47:10 om-gta02 user.warn kernel: JFFS2 warning: (1371)
jffs2_sum_write_sumnode: Not enough space for summary, padsize = -1157
Dec 15 03:47:35 om-gta02 user.info kernel: jbt6k74 spi2.0:  jbt6k74
unblank
Dec 15 03:48:17 om-gta02 user.info kernel: jbt6k74 spi2.0:  jbt6k74
powerdown

But it doesn't happen on every boot, this noon it didn't appear. And I
haven't had a freeze with SHR yet.
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: Other possible Echo Cause

[Al Johnson]

On Monday 15 December 2008, Paul wrote:
> I have been thinking about the possible causes for the echo bug.  I
> have a feeling that it's actually feedback and not an echo.  I think
> what's happening is the sound is being picked up by the mic and being
> sent to the remote phone for an extra round of fun.

I hadn't realised there was any doubt that this was the mechanism. 

> Does anyone know how I would start testing this?  In particular,  I
> would like to try the following.
>
> 1. Disable the mic totally and raise the handset volume.  I know the
> handset volume is set by Control.4 values in gsmhandset.state file.  I
> would make some phone calls and have the remote party talk to see if
> an echo occurs.  If not echo occurs, well then we know the mic is part
> of the cause.

If you mute either the mic or the earpiece there is no echo. If you use the 
wired headset there is no echo. The level of echo is affected by both the mic 
gain and the earpiece level. Using the speakerphone gives much more echo, 
which is expected because the volume is higher and the speaker is close to 
the mic.

> I also know that our telephone systems do not transmit the whole
> audible frequency range.  Is there a way to clip the audio from the
> mic for phone calls?  I think this would translate to
> reduce/elimination of buzz.

It's possible, but the buzz is within the voice frequency range. If we could 
characterise the buzz sufficiently it may be possible to remove it by 
applying a suitable digital filter in the CPU, but a hardware fix is 
certainly preferable.


___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: Sad Story

[arne anka]

> Karthik:
>
> I think I probably speak for a reasonable portion of the community when
> I say this:
>
> Go buy an iphone. Put your FreeRunner on ebay. You'll like the iphone -

+1

___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: pointless ranting was: Re: Sad Story

[arne anka]

>> if you refuse to check archives and to read mails and instead insist on
>> perpetuating your misstatement, nobody can help you!
>
> Then this link be updated. http://wiki.openmoko.org/wiki/GTA03


i give up.
you are deliberatly confusing things just to prove your point, imo.

eot for me.

___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: Sad Story

[Dale Maggee]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Karthik Kumar wrote:
>(Many many trollish and uninformed things)

Karthik:

I think I probably speak for a reasonable portion of the community when
I say this:

Go buy an iphone. Put your FreeRunner on ebay. You'll like the iphone -
it has DRM and you can buy software for it! And if you don't like it,
you can lodge a support ticket with Apple, who will be more than happy
to send you an automated response containing no real information...


-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFJRhyeFbVnQRV3OEYRAtRRAKCBWVHL+JPiblTmKhLQUvUD0Vf5PQCgqAFG
Cc9IZtW3AlGyxQnRhq/hDfA=
=o0K3
-END PGP SIGNATURE-

___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

German layout for usb keyboard?

[Konstantin]

Hi there!

I just got my mini-usb-keyboard for my freerunner, and I'm very happy that it
works "out of the box" - mostly, that is: How do I set a german layout for the
keyboard under X? Normally, I would have done it by editing the xorg.conf, but
since I can't find it, there has got to be another way, right?
Any help would be very much appreciated :)

Regards,
Konstantin

___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: Sad Story

[William Kenworthy]

You might do better to read back on the emails ... the hardware fix is
the kludge in my view - it is on one of the clock lines.  They did this
early on, and it did have an effect.  THEN they found that it was
improved by only clocking the SD card when neccessary (i.e., access).
Then lastly, they discovered that the clock drive was set too high
(max).

Once they had all the info, all the fixes were in (cap, correct drive
and SD card clocking on on access), things were good.  The cap seems to
have an effect, but is minor compared to the others, but its "in the
system" so stayed.  The majority of earlier FR's dont have it (including
mine) and work fine. Oh, and if you really want it, there's a SOP laying
out how to add it yourself.

Going from memory for the above, but it should be largely right.

BillK


On Mon, 2008-12-15 at 11:17 +0530, Karthik Kumar wrote:
> On Mon, Dec 15, 2008 at 5:35 AM, Stefan Monnier
>  wrote:
>  There are still hardware problems that exist with almost every
>  freerunner out there (GPS signal levels, for one).  I would like to
>  see them fixed by Openmoko, Inc.
> >> The kernel fix for GPS is a mere quirk. Ideally it should get fixed in
> >> hardware.
> >
> > Huh?  The kernel fix seems to work OK for those people who have old
> > FRs.  Newer FRs have a hardware fix.  E.g. my FR doesn't need any
> > kernel workaround.  No need to wait for GTA03 to get a hardware fix.
> 
> So, this kernel fix is a feature, according to Al Johnson? Then why do
> they need a hardware fix? Unless I am missing something, this software
> fix seems to be a lie. Or the hardware fix seems to be bogus anyway. I
> have one of the earlier freerunners released, so I'm sure Openmoko
> owes an explanation.
> 
> >
> >
> >Stefan
> >
> >
> >
> > ___
> > support mailing list
> > support@lists.openmoko.org
> > https://lists.openmoko.org/mailman/listinfo/support
> 
> ___
> support mailing list
> support@lists.openmoko.org
> https://lists.openmoko.org/mailman/listinfo/support
-- 
William Kenworthy 
Home in Perth!


___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: FreeRunner does not boot although battery o.k.

[Robin Paulson]

2008/12/15 Preben Holm :
> If I suspend the phone - I can't power it up again!
>
> I think it's a software issue, since the old version (2007.2) had no
> trouble with this.
> I'm running 2008.9 (as far as I remember).

have you got an up to date u-boot? lots of power problems have been
fixed with that. also, is the system up to date?

these commands:

opkg update
opkg upgrade

will do the latter; the former needs some flashing from the boot menu

by the way, if you're starting a new topic it would help if you could
create a new e-mail, and set the subject accordingly

cheers

___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: FreeRunner does not boot although battery o.k.

[Preben Holm]

If I suspend the phone - I can't power it up again!

I think it's a software issue, since the old version (2007.2) had no 
trouble with this.
I'm running 2008.9 (as far as I remember).


Best regards

Preben




Joachim Ott skrev:
> 2008/12/14 Timo Juhani Lindfors  >
>
> "Alexander Kappner"  > writes:
> > What can I do to bring my FreeRunner back to live?
>
> I am not an expert on hardware stuff but I would remove battery, sd
> card and sim card for a while. Then reinsert battery and try to boot
> to NOR uboot. If that fails then it really sounds like a bit more
> persistent hardware issue and might need to find somebody with the
> debug board to start figuring out what is going on.
>
>
>  It's okay to remove the battery for a while. You can remove SIM and 
> SD too if you like, but I'll give you (Timo) one sixpack for every 
> Volt you might find left in the SIM or SD.
>
> The first thing I would try a different battery or external power in 
> that case.
>
> 
>
> ___
> support mailing list
> support@lists.openmoko.org
> https://lists.openmoko.org/mailman/listinfo/support
>   


___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support