On Tuesday 22 July 2008 05:43, Simon Matthews wrote:
So the fact you were OK at drive level 0 should mean are able to use SD
card how you like without problems from SD_CLK to GPS any more.
Surely the hardware and software 'fixes' can only be seen as a total fix
if they make the SN (signal
Inside my house I generally loose the fix when the SD card
is stressed, not sure what will happen outside.
But that's only when really hammering the card, incidental usage does
not seem to affect the GPS performance in any way.
Could you elaborate on how did you exactly hammer the card?
Thanks for that Andy,
There are some numbers here:
http://git.openmoko.org/?p=kernel.git;a=commitdiff;h=66a83c97c4545ce4f07e0d90998f906fae49caf2
Could you tell me what exactly you are measuring, radiated power? and
under what conditions.
How was the noise floor measured.
Thanks Simon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Thanks for that Andy,
|
| There are some numbers here:
|
|
http://git.openmoko.org/?p=kernel.git;a=commitdiff;h=66a83c97c4545ce4f07e0d90998f906fae49caf2
|
|
| Could you tell me what exactly you are
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| So the fact you were OK at drive level 0 should mean are able to use SD
| card how you like without problems from SD_CLK to GPS any more.
|
| Surely the hardware and software 'fixes' can only be seen as a
On ti, 2008-07-22 at 11:43 +0800, Simon Matthews wrote:
Surely the hardware and software 'fixes' can only be seen as a total fix
if they make the SN (signal to noise ratio) of the GPS the same as if
the SD card is not present.
FWIW and IMAO, this definition of a total fix is impractical almost
So the fact you were OK at drive level 0 should mean are able to use
SD
card how you like without problems from SD_CLK to GPS any more.
If at all possible, can someone who understands this explain it so we
developers can add the hack/patch to our running Freerunners and
continue
Hey Andy,
will the patch be spread by opkg too?
I did some updates, but the sd_card file still does not appear.
Anything I missed?
thx in advance
Bastian
On Mon, Jul 21, 2008 at 2:11 AM, Andy Green [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| So the fact you were OK at drive level 0 should mean are able to use
| SD
| card how you like without problems from SD_CLK to GPS any more.
|
|
| If at all possible, can someone who understands this explain
I will change the default drive strength to 0 today, tomorrow's kernel
should just work. The SD Card we ship anyway seems to work fine
like
that.
okay great, i'll keep an eye out for that update tomorrow and test it
with my 8gig MicroSD card (kingston), which so far has been working
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Hey Andy,
| will the patch be spread by opkg too?
| I did some updates, but the sd_card file still does not appear.
|
| Anything I missed?
According to the filename, this uImage.bin has the patch in
According to the filename, this uImage.bin has the patch in
http://buildhost.openmoko.org/daily/freerunner/200807/20080722/uImage-2.6.24+git23+1d04b142ffeaa15129f046751f1366b0f0614f47-r0-om-gta02.bin
how did you tell? by looking at the md5sum?
btw: why can't these packages not simply have a
btw: why can't these packages not simply have a date in the name, maybe
with a time, too?
These signify which git tree/revision is built.
The date is in the folder names containing it.
doesn't help with opkg -- from looking at the package's name you cannot
tell if your kernel is from
Surely the hardware and software 'fixes' can only be seen as a total fix
if they make the SN (signal to noise ratio) of the GPS the same as if
the SD card is not present.
FWIW and IMAO, this definition of a total fix is impractical almost to
the point of uselessness. There will always
Hi,
So you mean the patch allowing to change the drive strength for SD,
not the latest patch you committed about 2 hours ago which set default
strength to 0 ?
On Tue, Jul 22, 2008 at 14:41, Andy Green [EMAIL PROTECTED] wrote:
Somebody in the thread at some point said:
| According to the
Hi Andy,
Can you do your voodoo so that this will install from opkg upgrade?
Thanks,
Vinc Duran
user
On Tue, Jul 22, 2008 at 6:01 AM, Andy Green [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| So the fact you were OK at
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| I know it is difficult to quantify this but it would be nice to know
| that say the clock current drive decrease by itself improved the SN
| ratio by say 6dB, the capacitor mod by itself improved the SN by
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| So you mean the patch allowing to change the drive strength for SD,
| not the latest patch you committed about 2 hours ago which set default
| strength to 0 ?
Yes, the now older patch introduced the /sys
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Hi Andy,
| Can you do your voodoo so that this will install from opkg upgrade?
That's someone else's voodoo, but it is the intention that it'll just
turn up in packages after 24hrs or less.
- -Andy
On Tue, 22 Jul 2008 17:34:58 +0200, Andy Green [EMAIL PROTECTED] wrote:
I guess you're not a kernel coder... not only is the segment for these
definitively zero at start of kernel, but it is an offence against
./scripts/checkpatch.pl to explicitly zero these things.
It's strange to have a
2008/7/20 Andy Green [EMAIL PROTECTED]:
Thanks for this report, I went and looked and found I didn't take care
of the case where last packet transferred was not a bulk read packet:
that what happens on resume. I added a patch to stable branch that
should be out tomorrow hopefully and give the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| This is now starting to look great! I seem to be unable to get the
Wah it's good to hear!
| It would be nice to know whether the S/N ratio is about as good with
| the software fix as it's without SD card
On Wed, Jul 16, 2008 at 9:01 AM, Edward A. Falk [EMAIL PROTECTED] wrote:
You do NOT get tech support like this anywhere else. Those of you
pounding your virtual fists on the table and demanding a fix *right now*
are out of line. The OpenMoko team is obviously working on it; give
them a
I'm really quite surprised it managed to ship in this condition, when
the fix is fundamentally a hardware one.
yikes. i think your record is broken ...
___
Openmoko community mailing list
community@lists.openmoko.org
On Mon, 21 Jul 2008 02:11:38 +0200, Andy Green [EMAIL PROTECTED] wrote:
Just a heads-up there is also another relevant patch on stable tonight.
~ It gives another interesting knob to twiddle about GPS performance.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| On Mon, 21 Jul 2008 02:11:38 +0200, Andy Green [EMAIL PROTECTED] wrote:
|
| Just a heads-up there is also another relevant patch on stable tonight.
| ~ It gives another interesting knob to twiddle about GPS
Andy Green, 2008-07-20 18:50:02 +0100 :
Thanks for this report, I went and looked and found I didn't take
care of the case where last packet transferred was not a bulk read
packet: that what happens on resume. I added a patch to stable
branch that should be out tomorrow hopefully and give
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Andy Green, 2008-07-20 18:50:02 +0100 :
|
| Thanks for this report, I went and looked and found I didn't take
| care of the case where last packet transferred was not a bulk read
| packet: that what happens
Andy Green wrote:
Just a heads-up there is also another relevant patch on stable tonight.
~ It gives another interesting knob to twiddle about GPS performance.
http://git.openmoko.org/?p=kernel.git;a=commitdiff;h=1d04b142ffeaa15129f046751f1366b0f0614f47
I did some tests with the new settings.
does it say what the two settings actually do?
Scott
Chris wrote:
Andy Green wrote:
Just a heads-up there is also another relevant patch on stable tonight.
~ It gives another interesting knob to twiddle about GPS performance.
look here:
http://git.openmoko.org/?p=kernel.git;a=commitdiff;h=1d04b142ffeaa15129f046751f1366b0f0614f47
Scott Derrick wrote:
does it say what the two settings actually do?
Scott
___
Openmoko community mailing list
community@lists.openmoko.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| sd_idleclk=1 and sd_drive=0:
| I can't see a weakening of the gps-signal. Signal strength seems as good
| as with sd_idleclk=0.
| I copied some (big) files to and from the card, none were corrupted, all
|
So the fact you were OK at drive level 0 should mean are able to use SD
card how you like without problems from SD_CLK to GPS any more.
Surely the hardware and software 'fixes' can only be seen as a total fix
if they make the SN (signal to noise ratio) of the GPS the same as if
the SD card is
Hello,
On Sun, Jul 20, 2008 at 5:03 AM, Yaroslav Halchenko
[EMAIL PROTECTED] wrote:
anyone knows if the software patch which was done has any hooks in user
space so the same procedure (shut off SD while getting FF) could be
initiated manually (from a script or so)?
AFAIK, the patch doesn't
On Sun, Jul 20, 2008 at 05:03, Yaroslav Halchenko
[EMAIL PROTECTED] wrote:
anyone knows if the software patch which was done has any hooks in user
space so the same procedure (shut off SD while getting FF) could be
initiated manually (from a script or so)?
The patch works like this:
When I/O
it is just that 'off while not active' seems to not explain why
Ville-Pekka Vainio reports effects of slow TTFF after suspend/resume
cycles... but let me just stop here -- I should just check out myself
instead of blurbing ;-)
On Sun, 20 Jul 2008, Torfinn Ingolfsen wrote:
Hello,
On Sun, Jul
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Timo Jyrinki wrote:
| Does anyone else have a reliability problem now with the new kernel
| and GPS when SD card is used?
|
| Yes, I just did some testing. The phone had been on for about 12 hours
maybe
|
Andy Green wrote:
Thanks for this report, I went and looked and found I didn't take care
of the case where last packet transferred was not a bulk read packet:
that what happens on resume. I added a patch to stable branch that
should be out tomorrow hopefully and give the same SD_CLK
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Andy Green wrote:
| Thanks for this report, I went and looked and found I didn't take care
| of the case where last packet transferred was not a bulk read packet:
| that what happens on resume. I added a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Timo Jyrinki a écrit :
2008/7/18 Timo Jyrinki [EMAIL PROTECTED]:
It seems it's not as good as without SD card, but definitely a visible
improvement.
Sorry for spamming, I just try to describe what I'm experiencing :)
Does anyone else have a
Timo Jyrinki, 2008-07-18 13:42:02 +0300 :
Does anyone else have a reliability problem now with the new
kernel and GPS when SD card is used?
Am Fr 18. Juli 2008 schrieb Roland Mas:
I have. Didn't manage to properly isolate the problem, but my gut
feeling is that Andy's patch to disable SD
2008/7/19 Roland Mas [EMAIL PROTECTED]:
Does anyone else have a reliability problem now with the new kernel
and GPS when SD card is used?
*Apparently*, there are
circumstances where running agpsgui once, getting a fix, exiting and
restarting afterwards, doesn't result in the FR getting a new
Timo Jyrinki wrote:
Does anyone else have a reliability problem now with the new kernel
and GPS when SD card is used?
Yes, I just did some testing. The phone had been on for about 12 hours maybe
and had gone through multiple suspend-wakeup cycles. TTFF was around 10
minutes. Then I switched
anyone knows if the software patch which was done has any hooks in user
space so the same procedure (shut off SD while getting FF) could be
initiated manually (from a script or so)?
On Sat, 19 Jul 2008, Ville-Pekka Vainio wrote:
Timo Jyrinki wrote:
Does anyone else have a reliability problem
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Do you know if the Antaris enters one of the sleep/backup modes
| on system power loss? If it does, perhaps it mode switch is triggered by
| external firmware. In backup mode it only consumes 8uA, and can
2008/7/17 Timo Jyrinki [EMAIL PROTECTED]:
| I tried the kernel too, but it didn't help. Didn't get any fixes in 3
| minutes when having SD card in (not in use, ie. maps not there).
| Removed the SD card and got a TTFF in 34 seconds.
I haven't seen any other readily available builds besides
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| But anyway, the great news is that this is definitely a big
| improvement. This is in a place where I used to be for half an hour
| without getting even UTC time from GPS if I used SD card, and now I'm
|
2008/7/18 Timo Jyrinki [EMAIL PROTECTED]:
It seems it's not as good as without SD card, but definitely a visible
improvement.
Sorry for spamming, I just try to describe what I'm experiencing :)
Does anyone else have a reliability problem now with the new kernel
and GPS when SD card is used? I
On 2008-07-18, Timo Jyrinki [EMAIL PROTECTED] wrote:
2008/7/18 Timo Jyrinki [EMAIL PROTECTED]:
It seems it's not as good as without SD card, but definitely a visible
improvement.
Sorry for spamming, I just try to describe what I'm experiencing :)
Does anyone else have a reliability
Andy Green wrote:
Yes GPS chip is very sticky, even when depowered for some time it
seems to hold state and not act in a deterministic way. It makes it
hard to know if the last thing you changed is responsible for the
behaviour staying the same or changing, or if it was going to do that
2. Tested GPS TTFF without SD card (from an indoor position not near a
window): 306s
3. Shutdown and insert SD card
4. Tested GPS TTFF with SD card (from same indoor position not near a
window): 484s
Nice test but I have a concern that only simulataneous test is a fair one
(two FR side
Am Fr 18. Juli 2008 schrieb JW:
Overall, getting indoor gps fix at all is pretty impressive - SIRF III is
great chipset.
Just we're using u-blox antaris chip ;-) (nearly as good, or maybe even
better)
/j
signature.asc
Description: This is a digitally signed message part.
Timo Jyrinki, 2008-07-18 13:42:02 +0300 :
Does anyone else have a reliability problem now with the new kernel
and GPS when SD card is used?
I have. Didn't manage to properly isolate the problem, but my gut
feeling is that Andy's patch to disable SD when acquiring the first
fix does only that
Am Fr 18. Juli 2008 schrieb Roland Mas:
Timo Jyrinki, 2008-07-18 13:42:02 +0300 :
Does anyone else have a reliability problem now with the new kernel
and GPS when SD card is used?
I have. Didn't manage to properly isolate the problem, but my gut
feeling is that Andy's patch to disable
On Wed, Jul 16, 2008 at 04:18:42PM +0200, Benedikt Schindler wrote:
hi,
i think the openmoko team is doing a great job.
and everyone was onto it, to have a fast and good solution.
so i think the real interesting question now is:
Had someone tested Andy's
I haven't seen a GPS device yet, including TomTom and
Garmin devices, that is completely free of defects during this stage
of
operation.
My Becker device has no problems whatsoever reading maps while
maintaining a very tight fix, and I've driven all over Austria and
never noticed such
Hi again,
On Wed, Jul 16, 2008 at 5:26 PM, nick loeve [EMAIL PROTECTED] wrote:
Hi Andy (nice work BTW, you and the rest of the team)
On Wed, Jul 16, 2008 at 5:02 PM, Andy Green [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
scott,
could you please disable html mails and send only plain text?
thanks
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Are we not pioneers of the open source mobile phone revolution?
And remember: It's the pioneers who take the arrows.
not if the go along well with the native tribes ... ;-)
___
Openmoko community mailing list
community@lists.openmoko.org
2008/7/17 nick loeve [EMAIL PROTECTED]:
I just tried the latest mwebster-andy kernel from
http://moko.mwester.net/dl.html#kernels which has the sdcard clock
patches, and now i get even better signals, and fix from cold start
outside in 48secs.
So the voltage patch certainly helped, and the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| 2008/7/17 nick loeve [EMAIL PROTECTED]:
| I just tried the latest mwebster-andy kernel from
| http://moko.mwester.net/dl.html#kernels which has the sdcard clock
| patches, and now i get even better signals,
Jay Vaughan schrieb:
If you can't understand why people would be frustrated to learn that
something as simple as testing GPS with the SD Card in the phone
hasn't been done, then you shouldn't be selling hardware.
So maybe you shold apply for the job of Head-Test-Designer and
[regarding Jay Vaughan]
*IF THIS ISSUE was that trivial, did you reported the solution?*
i think everything to be said is said already -- and more than once and
necessary.
while everybody is free to repeat those rants over and over if would be
for the best of the list if it could
STOP
Yeah, definitely with you on the 'moving on' part .. glad to see there
is a workaround for the GPS+SD problems, and I'm also watching the SD
+Glamo hacking with keen interest ..
j.
On Jul 17, 2008, at 2:19 PM, arne anka wrote:
[regarding Jay Vaughan]
*IF THIS ISSUE was that trivial, did
C'mon guys! I'm sick of all this s**t!! Jay, if you don't like
Freerunner go away and shut up, else stay but still shut up!
Jay Vaughan wrote:
div class=moz-text-flowed style=font-family: -moz-fixedYeah,
definitely with you on the 'moving on' part .. glad to see there is a
workaround for
I did an opkg update on the factory image last night (~7-8 PM PST), and
now GPS fix times are less than a minute. The update downloaded a new
kernel:
# opkg status kernel
Package: kernel
Version: 2:2.6.24+git20+287b292cf95edbd82dc63085ae5f0167a6e8141f-r0
Depends: kernel-2.6.24
Status: install
2008/7/17 Andy Green [EMAIL PROTECTED]:
|| http://moko.mwester.net/dl.html#kernels which has the sdcard clock
| I tried the kernel too, but it didn't help. Didn't get any fixes in 3
| minutes when having SD card in (not in use, ie. maps not there).
| Removed the SD card and got a TTFF in 34
Russell Sears wrote:
I did an opkg update on the factory image last night (~7-8 PM PST), and
now GPS fix times are less than a minute. The update downloaded a new
False alarm; the satellites must have been aligned last night... Fix
times are multiple minutes again...
-Rusty
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Russell Sears wrote:
| I did an opkg update on the factory image last night (~7-8 PM PST), and
| now GPS fix times are less than a minute. The update downloaded a new
|
| False alarm; the satellites must
Hi Andy, and thank you for your quick and focused efforts.
Do you know if the Antaris enters one of the sleep/backup modes
on system power loss? If it does, perhaps it mode switch is triggered by
external firmware. In backup mode it only consumes 8uA, and can
probably remain alive for a long time
Ever thought about I might feel personally offended by you
publically assuming
I sell hw I *know* or even have suspect there is a HW-bug in it.
Nope. I have not ever made that assumption. I assumed you didn't
know you had been selling buggy hardware. Thats the problem.
Did you
However,.. one must really think why this problem didn't turn out in
the
factory tests :-(
Yes. That is indeed something that must be thought about.
;
--
Jay Vaughan
___
Openmoko community mailing list
community@lists.openmoko.org
For something as evocative as this GPS/SD issue, I'd like to see at
*least* daily updates posted to an official website or blog (not
wiki).
Its really pretty important that the communication on this issue *not*
diverge into hate and vitriol towards customers, because to those who
are
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
To say the true I never saw a firm to admit the problem and to start to
work for a fix in 11h!
Steven Kurylo wrote:
On Tue, Jul 15, 2008 at 3:33 PM, Hugo Mills [EMAIL PROTECTED] wrote:
On Tue, Jul 15, 2008 at 04:50:50PM -0500, Robert Horton wrote:
On Wed, 2008-07-16 at 09:22 +0800, Wolfgang Spraul wrote:
Alejandro -
This issue does not look good. Is there someone in Openmoko or FIC
aware of it?
Aware of it? You must be kidding.
Dear Wolfgang,
there remains one question that the community has to you and it is even
more
Jay Vaughan wrote:
For something as evocative as this GPS/SD issue, I'd like to see at
*least* daily updates posted to an official website or blog (not
wiki).
Its really pretty important that the communication on this issue *not*
diverge into hate and vitriol towards customers,
To say the true I never saw a firm to admit the problem and to start
to
work for a fix in 11h!
Please do not ignore the fact that GPS has been complained about for
months.
;
--
Jay Vaughan
___
Openmoko community mailing list
Its really pretty important that the communication on this issue
*not*
diverge into hate and vitriol towards customers, because to those who
are observing the OpenMoko project - not participating - the SD+GPS
testing issue is a *huge* screw up.
No, the SD+GPS issue is a bug.
Marcus,
Why have you not used the phone yourselves?
We are using it.
Why are you abusing the community in such a shameless way?
We don't. We are just working as hard and smart as we can. A pretty
awesome group of people actually, and obviously our community
(including critical people like
Jay Vaughan wrote:
Its really pretty important that the communication on this issue
*not*
diverge into hate and vitriol towards customers, because to those who
are observing the OpenMoko project - not participating - the SD+GPS
testing issue is a *huge* screw up.
No, the SD+GPS
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Christoph Anton Mitterer a écrit :
On Wed, 2008-07-16 at 00:37 +0200, Flemming Richter Mikkelsen wrote:
This GPS problem shows a lot about the community vs openmoko.
Some try to help (developers?)
Some complain (regular users?)
A lot of regular
with us to any
test you need to be done
--- El mié, 16/7/08, Jay Vaughan [EMAIL PROTECTED] escribió:
De: Jay Vaughan [EMAIL PROTECTED]
Asunto: Re: Reason for GPS problems found!
Para: List for Openmoko community discussion community@lists.openmoko.org
Fecha: miércoles, 16 julio, 2008 8:50
Its
On Wed, Jul 16, 2008 at 12:01 AM, Wolfgang Spraul [EMAIL PROTECTED]
wrote:
On the GPS bug, expect an update before the end of the week.
Unfortunately, this seems like a case where OpenMoko's openness is really
hurting it. A closed company probably would have waited to publicly
acknowledge the
Marcus Bauer wrote:
On Wed, 2008-07-16 at 08:45 +0200, Kalle Happonen wrote:
Its really pretty important that the communication on this issue *not*
diverge into hate and vitriol towards customers, because to those who
are observing the OpenMoko project - not participating - the SD+GPS
On Wed, Jul 16, 2008 at 12:37:15AM -0700, Andrew Bennett wrote:
On the GPS bug, expect an update before the end of the week.
Unfortunately, this seems like a case where OpenMoko's openness is
really hurting it.
I disagree. I think it's great that we can see what goes on under the
hood,
Hi Jay-
Jay Vaughan ??:
To say the true I never saw a firm to admit the problem and to start
to
work for a fix in 11h!
Please do not ignore the fact that GPS has been complained about for
months.
I think this main reason is our test environment is badly synced
I also believe the GPS is a core feature of the phone and one area I
am slightly disappointed in is the testing. For example, there are
some experienced users of GPS here and some who have used GPS on the
1973 since it became usable. Were prototype Freerunners sent out to
these people? If so how
Wow, Jay. I think it may be time to step away from the computer and
calm down.
Okay, I've done this.
There may be a complete fix for this within a few days, so
there's little reason to write antagonistic messages to the very
people
who are working hard to fix this.
Its really important
2008/7/16 Jay Vaughan [EMAIL PROTECTED]:
Did you consider the public image that's being created by a
statement like Ah
well, this seems not to work. So the brick is useless for me. Damn
the day I bought it
If you can't understand why people would be frustrated to learn that
something as
From all the Openmoko employees nobody has realized that the GPS is
broken. Why have you not used the phone yourselves? Why are you abusing
the community in such a shameless way?
would you please be less insulting!
those personal abuses, not at least by jay in regard to joerg are not
helping
2008/7/15 Joerg Reisenweber [EMAIL PROTECTED]:
The good news: *IF* all pans out, there's (or soon will be) a new kernel at
Andy branch that stops SD-card clock when SDcard is idle. We hope this will
almost cure the problem, at least reduce it to sth like you can't GPS while
watching video from
On Wed, Jul 16, 2008 at 10:56 AM, Timo Jyrinki [EMAIL PROTECTED] wrote:
So, if it's not productive (or positive), please try to restrain
yourself from posting (there have been enough complains already).
I was expressing sad tone along with the other fellow, instead of
complaining. I think that
Timo Jyrinki wrote, On 16/07/08 09:56:
I don't think it helps either to make sure one's rights are listened
to - I think one reason people might complain is that they simply want
to create noise so that Openmoko knows it's important. Please, show a
little more respect and trust for them -
On Wednesday 16 July 2008, Jeffrey Ratcliffe wrote:
2008/7/15 Joerg Reisenweber [EMAIL PROTECTED]:
The good news: *IF* all pans out, there's (or soon will be) a new kernel
at Andy branch that stops SD-card clock when SDcard is idle. We hope this
will almost cure the problem, at least reduce
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeffrey Ratcliffe a écrit :
2008/7/15 Joerg Reisenweber [EMAIL PROTECTED]:
The good news: *IF* all pans out, there's (or soon will be) a new kernel at
Andy branch that stops SD-card clock when SDcard is idle. We hope this will
almost cure the
This will still be a problem for those GPS applications loading big
maps from SD, I assume.
Only if the GPS app is trying to read maps from SD during the time the
GPS is
getting the initial fix. Once we have the fix the required signal level
is
lower, so even with the SD enabled the
Am Mi 16. Juli 2008 schrieb Jay Vaughan:
Its really pretty important that the communication on this issue
*not*
diverge into hate and vitriol towards customers, because to those who
are observing the OpenMoko project - not participating - the SD+GPS
testing issue is a *huge* screw up.
On 2008-07-16, Jay Vaughan [EMAIL PROTECTED] wrote:
Its really pretty important that the communication on this issue
*not*
diverge into hate and vitriol towards customers, because to those who
are observing the OpenMoko project - not participating - the SD+GPS
testing issue is a *huge*
Am Mi 16. Juli 2008 schrieb Kalle Happonen:
Marcus Bauer wrote:
The same goes for making phone calls: there is quite often a buzzing
sound on the far end and it can be really bad. Unless you don't care
about the people you are calling the Neo is not usable as your daily
phone.
This
Am Mi 16. Juli 2008 schrieb Jay Vaughan:
However,.. one must really think why this problem didn't turn out in
the
factory tests :-(
Yes. That is indeed something that must be thought about.
;
--
Jay Vaughan
Tony Tu already posted a response to this: Our factory tests can't be
1 - 100 of 222 matches
Mail list logo
