arne anka wrote:
[...]
Echo reacts to some tweaking in alsa and maybe Calypso firmware
option selection, I guess this turn up in rootfs images as best it
can.
OK, but do you need to be so imprecise about this? What can't there
be a definitive solution?
because the echo is caused only
yes joerg has a DRAFT version of the SOP for the buzz fix rework of
A5/A6. Not everybody has the buzz issue.
1. It's a draft.
2. We need to have some independent test of the SOP
arne anka wrote:
buzz / echo / hiss... no software change can fix buzz. It's baked
into the hardware and you will
GTK support seems mildly improved in the testing release, but I'm
still having big troubles with it. Note, that relatively simple GTK
apps, such as TangoGPS work without issue.
We're running a complex GTK app: http://gvsigmobileonopenmoko.wordpress.com/
It works perfectly on 2007.2, but on
Am 08.12.2008 um 13:38 schrieb Joseph Reeves:
GTK support seems mildly improved in the testing release, but I'm
still having big troubles with it. Note, that relatively simple GTK
apps, such as TangoGPS work without issue.
We're running a complex GTK app:
2008/12/2 John Lee [EMAIL PROTECTED]:
On Mon, Dec 01, 2008 at 09:29:48PM +, Neil Jerram wrote:
Apologies in advance for what may be a dumb question - but does this
statement represent the conclusion of your team's work on audio issues
(buzz/echo/hiss etc.)? Or is there further work
2008/12/2 Andy Green [EMAIL PROTECTED]:
buzz / echo / hiss... no software change can fix buzz. It's baked
into the hardware and you will have to do fairly extreme meddling with
your soldering iron to impact it.
Thanks, I hadn't seen that so clearly stated before! (i.e. that buzz
is known to
Oops...
2008/12/7 Neil Jerram [EMAIL PROTECTED]:
OK, but do you need to be so imprecise about this? What can't there
be a definitive solution?
What should have been why.
Neil
___
Openmoko community mailing list
community@lists.openmoko.org
On Sun, 7 Dec 2008 15:22:58 +
Neil Jerram [EMAIL PROTECTED] wrote:
2008/12/2 Andy Green [EMAIL PROTECTED]:
buzz / echo / hiss... no software change can fix buzz. It's baked
into the hardware and you will have to do fairly extreme meddling
with your soldering iron to impact it.
buzz / echo / hiss... no software change can fix buzz. It's baked
into the hardware and you will have to do fairly extreme meddling
with your soldering iron to impact it.
Thanks, I hadn't seen that so clearly stated before! (i.e. that buzz
is known to be 100% a hardware issue).
On Sunday 07 December 2008, Neil Jerram wrote:
2008/12/2 Andy Green [EMAIL PROTECTED]:
buzz / echo / hiss... no software change can fix buzz. It's baked
into the hardware and you will have to do fairly extreme meddling with
your soldering iron to impact it.
Thanks, I hadn't seen that so
Thanks Jake.
I reviewed the SOP yesterday and Werner had a look at it as well.
There is a tiny bit of clean up ( spelling etc) and a couple little details.
( arrows on the photos) Also, I really would like to have somebody
external to Openmoko test the SOP by actually doing it. Maybe even
Hi All,
During today's upgrade I encountered the following error:
* ERROR: The following packages conflict with openmoko-phoneprofile-data:
* qtopia-phone-x11-profile-data *
How should I proceed? Uninstall one of these?
Regards,
Andreas
John Lee wrote:
Dear Community,
As
John Lee wrote:
On Fri, Dec 05, 2008 at 10:28:48AM +0100, Andreas Fischer wrote:
Hi All,
During today's upgrade I encountered the following error:
* ERROR: The following packages conflict with openmoko-phoneprofile-data:
* qtopia-phone-x11-profile-data *
How should I proceed?
Hi,
Joerg went over the change for a5/a6 with me the other night.
Over the next few days I'll drive to get an SOP published for
the change. But for now I'll just explain it in words. The
modification should work for both a5a6. It consists of:
1. Removing the front cover.
2.
Thanks Steve for this little insight.
As the mod doesn't seem that hard to do, I'm looking forward to my
Freerunner for christmas (regardless if its A7 or a not yet reworked
A6 :) ).
Jake
On Thu, Dec 4, 2008 at 1:46 PM, Steve Mosher [EMAIL PROTECTED] wrote:
Hi,
Joerg went over the change for
On Sun, 2008-11-30 at 19:50 +0800, John Lee wrote:
Dear Community,
As Sushama (our new testing team member) indicated in
http://lists.openmoko.org/pipermail/devel/2008-November/003493.html ,
we won't have a release in Nov. Currently the testing team is going
...
Ive been using this for a
On Tue, Dec 2, 2008 at 9:42 PM, Andy Green [EMAIL PROTECTED] wrote:
buzz / echo / hiss... no software change can fix buzz. It's baked
into the hardware and you will have to do fairly extreme meddling with
your soldering iron to impact it.
Would it be better to wait until A7 is out and then
Ticket #2157
Would be nice if anyone else is seeing this to pipe up too - starting to
feel its just me ...
BillK
On Wed, 2008-12-03 at 21:54 +0800, John Lee wrote:
On Sun, 2008-11-30 at 19:50 +0800, John Lee wrote:
Dear Community,
As Sushama (our new testing team member)
Jakob a écrit :
On Tue, Dec 2, 2008 at 9:42 PM, Andy Green [EMAIL PROTECTED] wrote:
buzz / echo / hiss... no software change can fix buzz. It's baked
into the hardware and you will have to do fairly extreme meddling with
your soldering iron to impact it.
Would it be better to wait
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Thanks your suggestion giving and thanks Andy. I am trying testing
| suspend/resume recursively with a script, using werner's wkalrm. If
| anything I get or any plan, anyway I will talk on kernl list,
On Tue, Dec 02, 2008 at 07:50:58PM +0900, William Kenworthy wrote:
On Mon, 2008-12-01 at 22:22 +0900, William Kenworthy wrote:
Thanks, also I was bit too rushed. I shut down X which allowed me to
Fonts and widgets are far too large on apps like pythm, tangogps and the
like.
John Lee wrote:
On Mon, Dec 01, 2008 at 05:31:37PM +0100, Andreas Fischer wrote:
Hi John, All,
Just upgraded from 2008.9. Things to mention:
- Boot time decreased. A lot! Thumbs up and a great Thank you for that :)
- Also, startup time for applications (dialer) seems to have decreased.
- As
Thats it. I installed my favourite gsmhandset.state which made the mic
audio acceptable. Then I modified PhoneProfile.conf as per #2140 and
have audio again.
I presume this fix (#2140) will appear in an update shortly?
Thanks.
BillK
On Mon, 2008-12-01 at 22:08 +0800, John Lee wrote:
On Mon,
On Mon, 2008-12-01 at 22:22 +0900, William Kenworthy wrote:
Thanks, also I was bit too rushed. I shut down X which allowed me to
Fonts and widgets are far too large on apps like pythm, tangogps and the
like.
...
Fixed by adding the gtkrc fix from FDOM
Should I raise a bug for this -
On Tue, Dec 02, 2008 at 10:49:47AM +0100, Andreas Fischer wrote:
John Lee wrote:
On Mon, Dec 01, 2008 at 05:31:37PM +0100, Andreas Fischer wrote:
Hi John, All,
Just upgraded from 2008.9. Things to mention:
- Boot time decreased. A lot! Thumbs up and a great Thank you for that :)
-
Upgraded to 0.2 - works fine.
BillK
On Mon, 2008-12-01 at 13:29 +, Thomas White wrote:
On Mon, 01 Dec 2008 22:22:28 +0900
William Kenworthy [EMAIL PROTECTED] wrote:
openmoocow (old version) started once out of three tries - left me at
a grey screen otherwise.
This is really my
William Kenworthy wrote:
Thats it. I installed my favourite gsmhandset.state which made the mic
audio acceptable. Then I modified PhoneProfile.conf as per #2140 and
have audio again.
I presume this fix (#2140) will appear in an update shortly?
I guess, since the openmoko OE tree has been
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Apologies in advance for what may be a dumb question - but does this
| statement represent the conclusion of your team's work on audio issues
| (buzz/echo/hiss etc.)? Or is there further work ongoing?
I've discovered the same:
https://docs.openmoko.org/trac/ticket/2148
Joseph
2008/12/1 William Kenworthy [EMAIL PROTECTED]:
Loaded it up and it rebooted fine, but isnt usable.
Ive lost the spanner so I cant configure it
It goes to sleep automaticly after a few seconds and without the
Thanks, also I was bit too rushed. I shut down X which allowed me to
stay logged in and find out that the customisations to get the spanner
and keyboards had been undone - fixed them and I can now use the phone.
The suspend time is fixable from the spanner so the settings isnt
needed.
Some of my
Loaded it up and it rebooted fine, but isnt usable.
Ive lost the spanner so I cant configure it
It goes to sleep automaticly after a few seconds and without the spanner
I cant figure out how to disable it (I see you mention that sleep time
needs to be reset - but how?). Same if I have it
On Mon, 01 Dec 2008 22:22:28 +0900
William Kenworthy [EMAIL PROTECTED] wrote:
openmoocow (old version) started once out of three tries - left me at
a grey screen otherwise.
This is really my fault, due to a combination of MooCow's architecture
in that version and the accelerometer driver
On Mon, Dec 01, 2008 at 10:22:28PM +0900, William Kenworthy wrote:
Thanks, also I was bit too rushed. I shut down X which allowed me to
stay logged in and find out that the customisations to get the spanner
and keyboards had been undone - fixed them and I can now use the phone.
The suspend
On Mon, Dec 01, 2008 at 10:22:28PM +0900, William Kenworthy wrote:
Thanks, also I was bit too rushed. I shut down X which allowed me to
stay logged in and find out that the customisations to get the spanner
and keyboards had been undone - fixed them and I can now use the phone.
The suspend
I've got:
[EMAIL PROTECTED]:~# opkg status moko-gtk-engine
Package: moko-gtk-engine
Version: 0.1.0+svnr4734-r0
Depends: moko-gtk-theme, gtk+ (= 2.12.11), libatk-1.0-0 (= 1.20.0),
pango (= 1.18.3), libcairo2 (= 1.6.4), libgobject-2.0-0 (= 2.16.4),
libgmodule-2.0-0 (= 2.16.4), libc6 (= 2.6.1),
On Mon, 1 Dec 2008 15:31:03 +
Joseph Reeves [EMAIL PROTECTED] wrote:
There seems to be a strange problem with gtk apps that, when first
loaded, they appear to freeze, but if you go back to home then
select the open app from the top drop down list again, they work fine.
It's an odd one to
Hi John, All,
Just upgraded from 2008.9. Things to mention:
- Boot time decreased. A lot! Thumbs up and a great Thank you for that :)
- Also, startup time for applications (dialer) seems to have decreased.
- As mentioned elsewhere, Enlightenment configuration was reset to not
show the spanner and
Thanks Tom,
Looks like _the_ big problem I've come across is well known to a fair
few people.
Cheers,
Joseph
2008/12/1 Thomas White [EMAIL PROTECTED]:
On Mon, 1 Dec 2008 15:31:03 +
Joseph Reeves [EMAIL PROTECTED] wrote:
There seems to be a strange problem with gtk apps that, when
2008/11/30 John Lee [EMAIL PROTECTED]:
Echo:
Since there are different hw versions out there (a5, a6, a7), it's
impossible to provide one alsa state file that suits all models.
However, it seems you can always find appropriate values for your
neo. My way is to adjust
control.4 Speaker
I'll reflash tonight and update, and investigate some of the other
problems as well. I need a phone so I've gone back to 2008.9 until
tonight :) Saving images makes it so much more flash friendly!
I dont think its fault, as the cow mooed quite fine before I updated.
It was really a hit at work
Thanks John, I'll reflash back to it tonight and provide feedback. If
its not volume, I'll raise a bug if I can figure out the cause. I am a
bit cautious of generalising this instance as I upgraded from a 2008.9
that has had bits from FDOM and elsewhere dropped into it.
BillK
On Mon,
On Mon, Dec 01, 2008 at 02:06:34PM +0800, John Lee wrote:
| * must remove 'ro' in kernel boot parameter if you use sd boot.
At the moment Qi has ro boot everywhere by default, is this restriction
just a temporary workaround for something?
I think it's related to Olv's new boot scripts. I
On Mon, Dec 01, 2008 at 05:31:37PM +0100, Andreas Fischer wrote:
Hi John, All,
Just upgraded from 2008.9. Things to mention:
- Boot time decreased. A lot! Thumbs up and a great Thank you for that :)
- Also, startup time for applications (dialer) seems to have decreased.
- As mentioned
On Mon, Dec 01, 2008 at 12:18:36AM +0300, Paul Fertser wrote:
Andy Green [EMAIL PROTECTED] writes:
Somebody in the thread at some point said:
| Hi,
|
| Andy Green [EMAIL PROTECTED] writes:
| For example some advice for Jeremy about suspend / resume issues
| would be don't waste your
On Mon, Dec 01, 2008 at 12:18:36AM +0300, Paul Fertser wrote:
And why the optimization team is still trying to fix bugs in Qtopia
and derivitaves? Let Nokia do their work, if they really want
to. Wouldn't it be better for the optimization team to hack on FSO or
at least (as they are in
On Mon, Dec 01, 2008 at 09:29:48PM +, Neil Jerram wrote:
2008/11/30 John Lee [EMAIL PROTECTED]:
Echo:
Since there are different hw versions out there (a5, a6, a7), it's
impossible to provide one alsa state file that suits all models.
However, it seems you can always find
great news,
but can't the opkg upgrade detect which hw revision we have and
install the best alsa state file?
afterall, good call quality is something almost everybody wants
y
On Sun, Nov 30, 2008 at 12:50 PM, John Lee [EMAIL PROTECTED] wrote:
Dear Community,
As Sushama (our new testing team
Or one could create a statefiles-metapackage and make the user choose his
model upon installation - or do this in package setup/configuration
scripts...
--
Marcel
Am Sunday 30 November 2008 13:01:47 schrieb Yorick Moko:
great news,
but can't the opkg upgrade detect which hw revision we have
On Sun, 30 Nov 2008 19:50:22 +0800
John Lee [EMAIL PROTECTED] wrote:
Echo:
Since there are different hw versions out there (a5, a6, a7), it's
impossible to provide one alsa state file that suits all models.
However, it seems you can always find appropriate values for your
neo. My way is
On Sun, Nov 30, 2008 at 07:50:22PM +0800, John Lee wrote:
Echo:
Since there are different hw versions out there (a5, a6, a7), it's
impossible to provide one alsa state file that suits all models.
However, it seems you can always find appropriate values for your
neo. My way is to adjust
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
Hi John -
| * some obsolete kernel modules still left in system
If we didn't do it already, the packaged kernels need to move to having
/lib/modules path that is specific to the kernel device and build,
Hi,
Andy Green [EMAIL PROTECTED] writes:
For example some advice for Jeremy about suspend / resume issues
would be don't waste your time doing any suspend / resume work on
2.6.24 kernel, only on andy-tracking.
I'm very sorry to jump in this thread. But this advice of yours is
so much
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Hi,
|
| Andy Green [EMAIL PROTECTED] writes:
| For example some advice for Jeremy about suspend / resume issues
| would be don't waste your time doing any suspend / resume work on
| 2.6.24 kernel, only on
Andy Green [EMAIL PROTECTED] writes:
Somebody in the thread at some point said:
| Hi,
|
| Andy Green [EMAIL PROTECTED] writes:
| For example some advice for Jeremy about suspend / resume issues
| would be don't waste your time doing any suspend / resume work on
| 2.6.24 kernel, only on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| What i'm trying to explain is that i see it as plain obvious that
| anybody who wants to work on a kernel stuff should coordinate their
| efforts on the kernel list. That anybody targeting fixing bugs in
On 30.11.2008 at 12:50:22, John Lee wrote:
Since there are different hw versions out there (a5, a6, a7), it's
impossible to provide one alsa state file that suits all models.
Just a short question: What is a7?
Can you please update the wiki article about the GTA02 revisions?
-- Fabian
On Sun, Nov 30, 2008 at 10:56:47PM +0100, Fabian Henze wrote:
On 30.11.2008 at 12:50:22, John Lee wrote:
Since there are different hw versions out there (a5, a6, a7), it's
impossible to provide one alsa state file that suits all models.
Just a short question: What is a7?
Can you please
On Sun, Nov 30, 2008 at 02:16:48PM +0100, Franky Van Liedekerke wrote:
On Sun, 30 Nov 2008 19:50:22 +0800
John Lee [EMAIL PROTECTED] wrote:
Echo:
Since there are different hw versions out there (a5, a6, a7), it's
impossible to provide one alsa state file that suits all models.
On Sun, Nov 30, 2008 at 01:32:20PM +, Rui Miguel Silva Seabra wrote:
On Sun, Nov 30, 2008 at 07:50:22PM +0800, John Lee wrote:
Echo:
Since there are different hw versions out there (a5, a6, a7), it's
impossible to provide one alsa state file that suits all models.
However, it seems
On Sun, Nov 30, 2008 at 06:56:28PM +, Andy Green wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
Hi John -
| * some obsolete kernel modules still left in system
If we didn't do it already, the packaged kernels need to move to having
60 matches
Mail list logo
