I opted for the G1, partly for the reasons you've given, but mainly because
it turned out to be available as a free upgrade from my old handset. I can't
say I'm terribly happy with it. I haven't had my hands on a Freerunner yet
for comparison, but depending upon what you want to do with your
Olivier Migeot wrote:
Community, you have this Openmoko company who is still working on
their product some months after it's been released. Granted, the first
release was nowhere near astounding. But in closed world developement,
who could claim such dedication? ;)
In a closed world
Gothnet schrieb:
Olivier Migeot wrote:
Community, you have this Openmoko company who is still working on
their product some months after it's been released. Granted, the first
release was nowhere near astounding. But in closed world developement,
who could claim such dedication? ;)
edit:
yes, the battery life sucks at the testing image (on 2008.9 i had 40
hours, which is not great, but since i come at least every second day,
this was not a problem)
---BeginMessage---
Gothnet schrieb:
Olivier Migeot wrote:
Community, you have this Openmoko company who is still
On Tue, 16 Dec 2008 11:46:01 pm Olivier Migeot wrote:
Due to some rather irritating bugs in QTE (high-pitched loud noises
from the loudspeaker when answering a call - quite disturbing for
co-workers - and duplicating text messages)
My guess with that is that's the phone going into
2008/12/10 t m ttb.1...@gmail.com
The goal of the optimization team was getting us a workable phone. I've
installed the testing version yesterday and run into a lot of issues (echo,
buzz, not able to wake up)
I love the idea of this phone, the openness, the capabilities, but my
patience has
On Tue, Dec 16, 2008 at 11:32 AM, Jeremy McNaughton
jeremy.mcnaugh...@gmail.com wrote:
Hi,
Just wanting to bring some balance to your (otherwise respectful)
comment. Not affiliated to OM, blabla, things like that.
I just wanted to chime in on this. I bought the phone not realizing
how
Hi,
I just wanted to chime in on this. I bought the phone not realizing
how useless as a phone it would be. And now it's been months, and I
still can't rely on it as a phone.
I was, and still am, excited about writing some python apps for the
phone. But frankly I don't see myself doing that
On 12/16/08 Jeremy McNaughton wrote:
Openmoko you have this community of users who are still enthusiastic
about your product. Do yourself a favour and learn how to keep us
interested by opening the lines of communication.
[snip]
Jeremy
Your post was very long with many points. Most
well put. I have not had time to get to the community list tonight-- err
this morning. I'll address as many of these as possible.
Sean Moss-Pultz wrote:
On 12/16/08 Jeremy McNaughton wrote:
Openmoko you have this community of users who are still enthusiastic
about your product. Do yourself a
On Thu, 11 Dec 2008 9:28:43 pm David Garabana Barro wrote:
1) If I want to receive calls with phone suspended, I have only one option:
SHR As SHR is based in FSO, I suppose you're right, FSO should also work.
But only SHR works out of the box. I have tried FSO M4, but I haven't
tried to force
On Monday 15 December 2008 11:18:03 Yogiz wrote:
On Mon, 15 Dec 2008 19:38:31 +1100
FWIW I can receive calls when suspected with Qt Extended.
As can I with 2008.9 testing.
I have tried all those, you can believe me. Even the latest OM testing image
fails for me.
I also suspect nearly all
On Mon, 15 Dec 2008 19:38:31 +1100
Chris Samuel ch...@csamuel.org wrote:
On Thu, 11 Dec 2008 9:28:43 pm David Garabana Barro wrote:
1) If I want to receive calls with phone suspended, I have only one
option: SHR As SHR is based in FSO, I suppose you're right, FSO
should also work. But
On Fri, Dec 12, 2008 at 2:11 AM, Steve Mosher st...@openmoko.com wrote:
Thanks david,
One of the difficulties is CND. cannot duplicate which complicates
finding the root cause. If you can generate logs that will probably help.
Steve
Perhaps say what should be run in the phone and what to
On Thursday 11 December 2008 02:23:14 Steve Mosher wrote:
RE 1024.
The optimization team was not working on 1024. there is one
dedicated engineer working on 1024 who specializes in this area. There
is some understanding but not certainty on the root cause which may be
related to the
On Wednesday 10 December 2008 12:11:53 arne anka wrote:
setting ti_calypso_deep_sleep = never.
That way, it drains a lot of battery even when suspended :(
don't see that with debian/fso -- i was afraid of it too, but mickey said
it wouldn't matter compared to the amount of power drawn by
setting ti_calypso_deep_sleep = never.
That way, it drains a lot of battery even when suspended :(
don't see that with debian/fso -- i was afraid of it too, but mickey
said
it wouldn't matter compared to the amount of power drawn by permanent
re-connecting ...
I know it, but this is
On Thu, Dec 11, 2008 at 10:55 AM, arne anka [EMAIL PROTECTED] wrote:
setting ti_calypso_deep_sleep = never.
That way, it drains a lot of battery even when suspended :(
don't see that with debian/fso -- i was afraid of it too, but mickey
said
it wouldn't matter compared to the
On Thursday 11 December 2008 10:55:35 arne anka wrote:
sorry, but i fail to understand how this relates to the question of power
consumption.
and doesn't shr use fso as well?
Sorry, I'm not explaying myself...
#1024 is annoying me a lot for two reasons
1) If I want to receive calls with
Thanks david,
One of the difficulties is CND. cannot duplicate which complicates
finding the root cause. If you can generate logs that will probably help.
Steve
David Garabana Barro wrote:
On Thursday 11 December 2008 02:23:14 Steve Mosher wrote:
RE 1024.
The optimization team was
On Wed, 2008-12-10 at 16:52 +0800, John Lee wrote:
Dear community,
I'm writing this to inform you that the optimization team is
dismissed, so there won't be weekly updates anymore. Further details
and reasons behind this are inappropriate to be answered by me.
And you switched your email
John Lee wrote:
Dear community,
I'm writing this to inform you that the optimization team is
dismissed, so there won't be weekly updates anymore. Further details
and reasons behind this are inappropriate to be answered by me.
What the heck? Are there any _long-term_ visions how to make
Steve, Sean, anybody more appropriate please clarify this ASAP, no
more resources in optimization?? crisis has arrive at least to
Openmoko Inc.??? It not sounds any good :( :(
2008/12/10 John Lee [EMAIL PROTECTED]:
Dear community,
I'm writing this to inform you that the optimization team
David,
the optimization team finished their work a few weeks ago, most people
were working on new tasks already.
I knew before I had to take the blame for expectations that got
unprofessionally raised to a level where we could not deliver, and
here I am now taking the blame.
Let me explain
the panic about where openmoko puts their efforts in...
panic for NO REASON.
sorry no offence but, i think it is because of the infacy of some users,
which can't hande information and start running around in circles
screaming fire, fire fire!.
i am sure there will still be optimization, but
Le mercredi 10 décembre 2008, Wolfgang Spraul a écrit :
David,
the optimization team finished their work a few weeks ago, most people
were working on new tasks already.
I knew before I had to take the blame for expectations that got
unprofessionally raised to a level where we could not
sorry no offence but, i think it is because of the infacy of some users,
which can't hande information and start running around in circles
screaming fire, fire fire!.
sentences like these
dismissed, so there won't be weekly updates anymore. Further details
and reasons behind this are
Wolfgang Spraul [EMAIL PROTECTED] writes:
---2 Mickey's framework milestones
As many people know, the next big thing for Openmoko will be Mickey's
FSO framework around d-bus and Python, and the Paroli telephony UI.
Thank you very much for this overview of strategy.
I have used
On Wed, Dec 10, 2008 at 12:53:18PM +0200, Timo Juhani Lindfors wrote:
However, I am bit puzzled about building on top of a new graphical
toolkit (EFL). Wouldn't we avoid many problems by using established
toolkits like QT or GTK+? The UI is supposed to be light so it should
be easy to port it
setting ti_calypso_deep_sleep = never.
That way, it drains a lot of battery even when suspended :(
don't see that with debian/fso -- i was afraid of it too, but mickey said
it wouldn't matter compared to the amount of power drawn by permanent
re-connecting ...
Rui Miguel Silva Seabra [EMAIL PROTECTED] writes:
EFL isn't exactly new, just not so popular as gtk+ or qt.
Heh, maybe I'm just being a bit debian centric here. I saw
libecore0 - Core abstraction layer for enlightenment DR 0.17
in debian experimental and thought that it can't be too
Wolfgang Spraul [EMAIL PROTECTED] writes:
Our current stable image is called 'Om2008.9', available at
http://downloads.openmoko.org/releases/Om2008.9/
We are sometimes cherry-picking fixes into it, but admittedly not as
many as we would like. If someone wants to step up to become stable
Yes - could we have a definitive answer on whether there will be a
2008.12 release of the current testing?
I seem to remember that a few weeks ago it was nearly ready and it was
almost certainly going to be 2008.11, clearly it slipped...
Cheers,
- Gunnar
Timo Juhani Lindfors wrote:
Wolfgang
Hi,
On Wed, 2008-12-10 at 18:13 +0800, Wolfgang Spraul wrote:
The latest image, including all optimizations from the optimization
team are in
http://downloads.openmoko.org/daily/testing/
(openmoko-testing-om)
We were testing this image a bit, haven't seen the full test report
yet.
Bernd,
i am sure there will still be optimization, but without a dedicated
team, so there won't be regular updates.
Correct.
From my perspective the updates weren't helpful anyway, I'd rather
not talk and instead deliver.
The latest image, including all optimizations from the optimization
On Wed, Dec 10, 2008 at 7:44 AM, Timo Juhani Lindfors
[EMAIL PROTECTED] wrote:
Heh, maybe I'm just being a bit debian centric here. I saw
libecore0 - Core abstraction layer for enlightenment DR 0.17
in debian experimental and thought that it can't be too established or
un-new.
I would
On Wednesday 10 December 2008 10:58:36 Wolfgang Spraul wrote:
David,
the optimization team finished their work a few weeks ago, most people
were working on new tasks already.
The most wanted improvement of the optimization team was, at least for me, a
solution to #1024.
I still suffer it.
Wolfgang thanks a lot for this clear development guide, It really
clear my mind and I'm anxious to follow,test and play with all the
steps you have mentioned, I will try to helps as much as I can in this
line.
2008/12/10 Wolfgang Spraul [EMAIL PROTECTED]:
David,
the optimization team finished
2008/12/10 Minh Ha Duong [EMAIL PROTECTED]:
Second: Basing FDOM on 2008.testing seems even more a good idea now. Given
that the official plan does not seem to include its release to the masses.
I'm doing my best to have a release soon thanks for the support :)
eeeuhm
this is no fix... yes it consumes less globally than with the constant
reconnecting,
but a ton of c4 is also less harmful than an nuclear bomb
doesn't mean we have to be happy with a ton of c4 in our pocket...
On Wed, Dec 10, 2008 at 12:11 PM, arne anka [EMAIL PROTECTED] wrote:
Yorick Moko [EMAIL PROTECTED] writes:
this is no fix... yes it consumes less globally than with the constant
reconnecting,
but a ton of c4 is also less harmful than an nuclear bomb
doesn't mean we have to be happy with a ton of c4 in our pocket...
It's better than without the fix so this
The goal of the optimization team was getting us a workable phone. I've
installed the testing version yesterday and run into a lot of issues (echo,
buzz, not able to wake up)
I love the idea of this phone, the openness, the capabilities, but my
patience has been stretched beyond tolerance. I have
Will Siddall wrote:
On Wed, Dec 10, 2008 at 7:44 AM, Timo Juhani Lindfors
[EMAIL PROTECTED] wrote:
Heh, maybe I'm just being a bit debian centric here. I saw
libecore0 - Core abstraction layer for enlightenment DR 0.17
in debian experimental and thought that it can't be too established or
arne anka wrote:
sorry no offence but, i think it is because of the infacy of some users,
which can't hande information and start running around in circles
screaming fire, fire fire!.
sentences like these
dismissed, so there won't be weekly updates anymore. Further details
and reasons
Wolfgang Spraul wrote:
the optimization team finished their work a few weeks ago, most people
were working on new tasks already.
Mmhmh... I was just thinking... What about the python-loader?
If I don't remember wrong, the optimization team had also the task of
creating a python loader to
RE 1024.
The optimization team was not working on 1024. there is one
dedicated engineer working on 1024 who specializes in this area. There
is some understanding but not certainty on the root cause which may be
related to the base station rather than the phone. I don't intend to
46 matches
Mail list logo
