Yes, this must be the problem. Thank you for your advise and I'll try
to fix this hardware problem.
On Tue, Apr 20, 2010 at 1:59 AM, Florian Franzmann
siflf...@hawo.stw.uni-erlangen.de wrote:
On Mon, 19 Apr 2010 21:21:41 +0300
Alex Theotokatos alex.the...@gmail.com wrote:
Hallo.
I have a
On Mon, Apr 19, 2010 at 11:21 AM, Alex Theotokatos
alex.the...@gmail.com wrote:
But when I insert sim card and I use it as shell phone with 2-3 short
phone calls, a full charged battery with suspends e.t.c. takes 18
hours to discharge.
i only get that kind of battery life if im using gps
On Mon, 19 Apr 2010 21:21:41 +0300
Alex Theotokatos alex.the...@gmail.com wrote:
Hallo.
I have a freerunner a7 and I bought it 3 months ago.
The battery lifetime is too short...
I mean, when I use it as regular computer, a full charged battery with
suspends e.t.c. takes almost two days to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| I've noticed significantly reduced runtime when using one of the
| latest daily builds (2008-07-16 I think). I have a theory. I suspect
| bluetooth isn't really being turned off when I think it is any
what's the hungriest of all? or if we can have a list of all the hungry
stuff in the FR sorted from the one starving to the one who needs a snack?
:)
On Sun, Jul 20, 2008 at 10:02 PM, Andy Green [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at
Use /usr/bin/hcitool scan from net-wireless/bluez-utils (gentoo) -
this picks up any promiscuous bluetooth transmitters in range.
BillK
On Sat, 2008-07-19 at 09:54 -0500, Steven ** wrote:
I've noticed significantly reduced runtime when using one of the
...
build completely drained the battery
Am So 20. Juli 2008 schrieb Flyin_bbb8:
what's the hungriest of all? or if we can have a list of all the hungry
stuff in the FR sorted from the one starving to the one who needs a snack?
GSM-active-call/GPRS data TX [up to 2A peak, 1A avg]
(USB-host mode [up to [EMAIL PROTECTED])
LCM-light
I've noticed significantly reduced runtime when using one of the
latest daily builds (2008-07-16 I think). I have a theory. I suspect
bluetooth isn't really being turned off when I think it is any more.
The factory image ran with a dimmed screen (no suspend) for a good 6
hours and only drained
I just got a running SIM card :-)
My FR likes to resume at lease once a min. If you were to take a
stealth approach, it would be doing 100's of resumes in a day. Which
is fine, if you want to test resume ;-)
I think we need to block this at a uBoot level. Perhaps a black list of
events?
-Adam
Am Fr 18. Juli 2008 schrieb Adam Talbot:
I just got a running SIM card :-)
My FR likes to resume at lease once a min. If you were to take a
stealth approach, it would be doing 100's of resumes in a day. Which
is fine, if you want to test resume ;-)
What's wrong with 100's of resumes / day,
What's wrong with 100's of resumes / day, as long as each one takes no
longer
than 2~3sec, and is on low power profile?
the screen becomes senstive to tapping -- and if your fr is in a place
where taps to the screen might occur frequently (say in your bag) it will
never suspend.
btw: are
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| What's wrong with 100's of resumes / day, as long as each one takes no
| longer
| than 2~3sec, and is on low power profile?
|
| the screen becomes senstive to tapping -- and if your fr is in a place
| where
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Backlight should be fixed for a couple of days now:
|
|
http://git.openmoko.org/?p=kernel.git;a=commitdiff;h=db07519c1dfe916bcf9644
| bfdc4d7c03707a979e
|
| That's good to hear, thanks. Will this be in the
Andy Green, 2008-07-18 10:29:54 +0100 :
Somebody in the thread at some point said:
| What's wrong with 100's of resumes / day, as long as each one takes no
| longer
| than 2~3sec, and is on low power profile?
|
| the screen becomes senstive to tapping -- and if your fr is in a place
|
It seems I was a little too ambitious with this test. I ran apm -s
and then went to bed. I woke up to a spiffy dead battery less than 6
hours later. :-/
-Steven
On Wed, Jul 16, 2008 at 11:11 PM, Adam Talbot [EMAIL PROTECTED] wrote:
I am currently using the 20080716 build, from:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Andy Green, 2008-07-18 10:29:54 +0100 :
|
| Somebody in the thread at some point said:
| | What's wrong with 100's of resumes / day, as long as each one takes no
| | longer
| | than 2~3sec, and is on low
You and Arne are quite right, suspend is subject to random wakes from
GSM world too at the moment and that can lead to the same result.
Carsten wants to deal with wakes in his daemon so we're waiting on that.
is there a way to detect when it wakes? a hook to plug custom actions
into? then,
Am Fr 18. Juli 2008 schrieb arne anka:
Touchscreen is not a wake from suspend source, so as you suggest it
didn't get to suspend to make this trouble.
not sure i understand you correctly, but several times i experience that
the fr, while seemingly in suspended state, answers to a screen
Am Fr 18. Juli 2008 schrieb arne anka:
You and Arne are quite right, suspend is subject to random wakes from
GSM world too at the moment and that can lead to the same result.
Carsten wants to deal with wakes in his daemon so we're waiting on that.
is there a way to detect when it
And what is it that stops us from disabling ts, just reenabling it when
we see
a valid wake-source to stay in user-land (e.g. inbound call, RTC,
powerbutton...)?
my question exactly.
___
Openmoko community mailing list
arne anka, 2008-07-18 15:09:01 +0200 :
is there a way to detect when it wakes? a hook to plug custom
actions into?
You might try sticking a script in /etc/apm/resume.d, at least as a
first approach.
Roland.
--
Roland Mas
Certains disent que les vrais hommes ne font pas de backups.
Mais ils
I'm thinking of getting out of this mailing list because it fills up my inbox
each day. Can someone please create a forum instead. I've been part of a lot of
mailing lists and this one is too much.
Mathieu Rochette [EMAIL PROTECTED] wrote:
On Thu, Jul 17, 2008 at 10:41 PM, Andy Green [EMAIL
I'm thinking of getting out of this mailing list because it fills up my
inbox each day. Can someone please create a forum instead. I've been
part of a lot of mailing lists and this one is too much.
please, check the archives and the wiki -- there are fora already.
else you could follow the
Friday 18 July 2008 arne anka wrote:
I'm thinking of getting out of this mailing list because it fills up my
inbox each day. Can someone please create a forum instead. I've been
part of a lot of mailing lists and this one is too much.
please, check the archives and the wiki -- there are
On Fri, 18 Jul 2008 14:01:59 +0100 Andy Green [EMAIL PROTECTED] babbled:
You and Arne are quite right, suspend is subject to random wakes from
GSM world too at the moment and that can lead to the same result.
Carsten wants to deal with wakes in his daemon so we're waiting on that.
waiting on
On Fri, 18 Jul 2008 06:30:23 -0700 (PDT) Pomeroy Lab
[EMAIL PROTECTED] babbled:
I'm thinking of getting out of this mailing list because it fills up my inbox
each day. Can someone please create a forum instead. I've been part of a lot
of mailing lists and this one is too much.
no - this has
On Fri, 18 Jul 2008 15:12:45 +0200 Joerg Reisenweber [EMAIL PROTECTED]
babbled:
Am Fr 18. Juli 2008 schrieb arne anka:
Touchscreen is not a wake from suspend source, so as you suggest it
didn't get to suspend to make this trouble.
not sure i understand you correctly, but several
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| On Fri, 18 Jul 2008 14:01:59 +0100 Andy Green [EMAIL PROTECTED] babbled:
|
| You and Arne are quite right, suspend is subject to random wakes from
| GSM world too at the moment and that can lead to the same
waiting on backlight to be left alone. daemon is done and already in ASU
and
being used by both illume and qtopia. backlight will come on on wake
right now
regardless until ompower (the daemon) changes its policy (code). :)
how toolkit specific is that daemon?
i do use 2007.2 and would
On Fri, 18 Jul 2008 15:29:32 +0100 Andy Green [EMAIL PROTECTED] babbled:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| On Fri, 18 Jul 2008 14:01:59 +0100 Andy Green [EMAIL PROTECTED] babbled:
|
| You and Arne are quite right, suspend is subject
arne anka wrote:
I'm thinking of getting out of this mailing list because it fills up my
inbox each day. Can someone please create a forum instead. I've been
part of a lot of mailing lists and this one is too much.
please, check the archives and the wiki -- there are fora already.
else
On Fri, 18 Jul 2008 16:34:05 +0200 arne anka [EMAIL PROTECTED] babbled:
waiting on backlight to be left alone. daemon is done and already in ASU
and
being used by both illume and qtopia. backlight will come on on wake
right now
regardless until ompower (the daemon) changes its
please also test http://lists.openmoko.org/nabble.html
that's great -- another step towards an one-stop.
in opera it is rendered as an iframe to small to fit so the content needs
scrolling -- but with firefox3 it is no iframe but simply cut off if the
window is too small.
resizing the window
On Sat, 19 Jul 2008 00:36:53 +1000 Carsten Haitzler (The Rasterman)
[EMAIL PROTECTED] babbled:
On Fri, 18 Jul 2008 15:29:32 +0100 Andy Green [EMAIL PROTECTED] babbled:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| On Fri, 18 Jul 2008
On Fri, 18 Jul 2008 06:30:23 -0700 (PDT) Pomeroy Lab wrote:
I'm thinking of getting out of this mailing list because it fills up
my inbox each day. Can someone please create a forum instead. I've
been part of a lot of mailing lists and this one is too much.
You can read this mailing list
I agree, I think it should be split, its getting out of hand.
Hardware
Software Applications
Software Kernel/Boot
Administrator
etc
Scott
Pomeroy Lab wrote:
I'm thinking of getting out of this mailing list because it fills up my
inbox each day. Can someone please create a forum instead.
On Wed, Jul 16, 2008 at 07:33:18AM -0700, Adam Talbot wrote:
dimlock != suspend :-)
If the screen is off, the system is still fully running, and sucking
down power. When you suspend, all running processes are cashed into
ram, then the rest of the hardware is turned off, with the exception
Hi,
I just installed script, and made a menu command for it to see what it
does to my battery. However, the phone wakes up inside a few minutes.
Someone earlier wrote:
That's currently the crux of the problem, and why I don't yet use suspend. It
resumes on cell registration messages, and each
Dim+nolock is choosen, as dim+lock seems to crash the device and I have
to remove the battery to reboot (nothing else works). Does anybody else
dim+lock is supposed to wake only when you touch the power button, imo.
___
Openmoko community mailing
On Wed, 2008-07-16 at 20:12 -0600, Scott Derrick wrote:
you got a SD card plugged in?
Nope (due to our GPS issue ;) )
smime.p7s
Description: S/MIME cryptographic signature
___
Openmoko community mailing list
community@lists.openmoko.org
apm -s
???
-Adam
On Thu, 2008-07-17 at 01:09 -0700, Ken Restivo wrote:
On Wed, Jul 16, 2008 at 07:33:18AM -0700, Adam Talbot wrote:
dimlock != suspend :-)
If the screen is off, the system is still fully running, and sucking
down power. When you suspend, all running processes are cashed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Hi,
|
| Am Mittwoch, den 16.07.2008, 13:17 -0600 schrieb Scott Derrick:
| Will the phone answer calls in suspend mode? Get text messages?
|
| If I suspend I haven't turned it into a dumb brick right?
|
| I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Hi,
| I just installed script, and made a menu command for it to see what it
| does to my battery. However, the phone wakes up inside a few minutes.
| Someone earlier wrote:
|
| That's currently the crux of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Subject to wakeups caused by cell reregistration this is true. This
isn't a
| complaint - keep reading ;-) It does a wake to full backlight too,
which is
| distracting and wastes power
Backlight should be
On Thu, Jul 17, 2008 at 10:41 PM, Andy Green [EMAIL PROTECTED] wrote:
Carsten has started on a daemon to handle wakes in userspace that should
eventually parse this and figure out if it can go back to suspend
silently once the wake reason was serviced.
should it be possible to disable a
On Thursday 17 July 2008, Andy Green wrote:
Somebody in the thread at some point said:
| Subject to wakeups caused by cell reregistration this is true. This
isn't a
| complaint - keep reading ;-) It does a wake to full backlight too,
which is
| distracting and wastes power
Backlight
Am Do 17. Juli 2008 schrieb Mathieu Rochette:
On Thu, Jul 17, 2008 at 10:41 PM, Andy Green [EMAIL PROTECTED] wrote:
Carsten has started on a daemon to handle wakes in userspace that should
eventually parse this and figure out if it can go back to suspend
silently once the wake reason
Ken,
I'm looking for possible solutions or areas to investigate.
When my FR's arrive I was going to investigate this area, but wondered
how easy it would be without a debug board..
Scott
Ken Restivo wrote:
On Tue, Jul 15, 2008 at 08:19:38PM -0600, Scott Derrick wrote:
I'm amazed that
Wow thats fantastic! First I have heard.
Gladly I will admit to raising a non-issue, sorry.
Scott
Adam Talbot wrote:
This is all with my FreeRunner.
144 hours, to be exact. Or, about 6 days of stand by time. Something
like 4 hours of active talk time. Looks like you could get 8 days and 5
This is how I do it.
http://wiki.openmoko.org/wiki/User:Nomeata
On Wed, 2008-07-16 at 14:50 +0200, arne anka wrote:
Wow thats fantastic! First I have heard.
Gladly I will admit to raising a non-issue, sorry.
i absolutely don't think it is a non-issue -- on the contrary!
besides tony tu
This is how I do it.
http://wiki.openmoko.org/wiki/User:Nomeata
read it already, but that should basically be the same as dimlock,
shouldn't it?
___
Openmoko community mailing list
community@lists.openmoko.org
dimlock != suspend :-)
If the screen is off, the system is still fully running, and sucking
down power. When you suspend, all running processes are cashed into
ram, then the rest of the hardware is turned off, with the exception of
the GMS modem, and ram.
Check out the S3 state:
dimlock != suspend :-)
i learned yesterday that
dimlock == suspend
and the messages scrolling over the screen before the lock screen comes
back when [pressing pwr | incoming call | fr wakes up frequently] prove
that imho.
dim!lock != suspend
thomasg wrote:
Where ever you think you might have heard this: it's bullshit.
Complete bullshit.
Which of this? I agree with Scott, well, in a more understanding, and
smiling way but still. I took the phone from the charger this morning,
and it's almost dead now at the end of the workday,
I am not sure what you are referring to as bullshit. I have a
FreeRunner, and am getting about 7 days of run time from it. In the
last 10days, sense I got it, I have only needed to charge it once. If
you think this is crap, then prove me wrong! Log into your FR and
execute an 'apm -s'. Give it
my freerunner will arrive this week, but don't worry, i'm a true believer :)
maybe it would help if there was standard a button to click on to
suspend the phone (maybe label it Suspend(Bèta)) because it seems most
people are not aware of something other than dimlock
On Wed, Jul 16, 2008 at 5:09
Yorick Moko wrote:
maybe it would help if there was standard a button to click on to
suspend the phone (maybe label it Suspend(Bèta)) because it seems most
people are not aware of something other than dimlock
If someone's going to get into adding buttons:
Our group last night agreed having a
Chris,
you got a SD card plugged in?
Scott
Christoph Anton Mitterer wrote:
How are you doing this?
If I fully charge my GTA02 battery before I go to bed,.. it will be
nearly empty when I wake up (I seep 7-8 hours),...
Dim+nolock is choosen, as dim+lock seems to crash the device and I have
I too am using the 2007.2 image upgraded. But I have no problem with
dim+lock. I haven't had my FreeRunner for long enough to definitively
say how long the battery will last. But I had it at work today,
showing it off several times. The remaining time it mostly sat on my
desk with dim+lock (I
I am currently using the 20080716 build, from:
http://buildhost.openmoko.org/daily/freerunner/200807/
Try running the apm -s That will suspend to ram. I do this by hand
every time I want the phone to suspend. The power button, or a call will
wake it. Please keep in mind, suspend to ram is
On Tue, Jul 15, 2008 at 08:19:38PM -0600, Scott Derrick wrote:
I'm amazed that more isn't being said about the battery lifetime people
are seeing?
I just read an article in Information Week that cited a large poll
concerning users of mobile devices. What was the number 1 issue, far
and
This is all with my FreeRunner.
144 hours, to be exact. Or, about 6 days of stand by time. Something
like 4 hours of active talk time. Looks like you could get 8 days and 5
of talk, but I like every thing turned on. I have GPS running, but with
out an SD card ;-). Currently using the built in
This is great news indeed! Since I'm adventurous, and thought I'd take
the Freerunner into phone use immideately, this has been the biggest
obstacle for normal use so far. With decent battery life I'd be a Very
Happy User.
Adam Talbot wrote:
This is all with my FreeRunner.
144 hours, to be
63 matches
Mail list logo
