after the latest debian updates, my fr loses connection to network after
suspending (or rather resuming).
i cant' call and looking into the tower info tab of zhone i get
MCC/MNC: 262/03
Serving Cell: N/A
restarting zhone (and being able to register) solves that -- until the
next suspend/resume
On Wed, 5 Aug 2009 11:30:33 pm Damian Spriggs wrote:
Fix for incoming call to voicemail bug:
Hmm, whilst it means I can place outgoing calls it still seems like every time
I reboot Android it goes back to all calls diverted to voicemail and I need to
manually tell it to to go and
On Wed, 5 Aug 2009 11:30:33 pm Damian Spriggs wrote:
Fix for incoming call to voicemail bug:
http://www.mail-archive.com/android-freerun...@android.koolu.org/msg01047.html
Thanks so much for that, it seemed to fix that problem!
Also found this nice little application to import contacts from a
On Thu, 6 Aug 2009 07:16:23 pm Chris Samuel wrote:
Hmm, whilst it means I can place outgoing calls it still seems like every
time I reboot Android it goes back to all calls diverted to voicemail and I
need to manually tell it to to go and automatically register on the network
Scratch that, I
Hi folks,
Does anyone know if the Android images at:
http://panicking.kicks-ass.org/download/
does suspend/resume at all ?
I last tried the Koolu ones a few months back and I don't believe they could
suspend/resume at all..
cheers,
Chris
--
Chris Samuel : http://www.csamuel.org
Chris Samuel wrote:
I last tried the Koolu ones a few months back and I don't believe they could
suspend/resume at all..
Hi Chris,
I don't know about the panicking image, but the koolu cupcake alpha 1
image suspends fine for me: http://koolu.org/releases/cupcake-1.5-alpha1/
Cheers,
Mike
On Wed, 5 Aug 2009 09:54:13 pm Michael Sheldon wrote:
I don't know about the panicking image, but the koolu cupcake alpha 1
image suspends fine for me: http://koolu.org/releases/cupcake-1.5-alpha1/
Sadly it appears that this image still has the issues of not registering
correctly with
Fix for incoming call to voicemail bug:
http://www.mail-archive.com/android-freerun...@android.koolu.org/msg01047.html
On Aug 5, 2009, at 9:06 AM, Chris Samuel wrote:
On Wed, 5 Aug 2009 09:54:13 pm Michael Sheldon wrote:
I don't know about the panicking image, but the koolu cupcake alpha 1
Am Dienstag, den 28.07.2009, 21:35 +0200 schrieb arne anka:
is there any infrastructure to run scripts upon suspend resp resume?
the only way so far seems to be using apmd -- but that adds considerable
delay to resume ...
I have seen some tickets wrt. that in the FSO bugtracker. We'll work
This probably isn't exactly what you're looking for, but...
I believe /etc/enlightenment/suspend.sh is the file ran to cause the
suspend. You could modify that. I don't know if there's an
equivalent for resume.
That suspend script uses FSO. And it seems like FSO calls the Resume
function of
is there any infrastructure to run scripts upon suspend resp resume?
the only way so far seems to be using apmd -- but that adds considerable
delay to resume ...
I don't remember exactly where, but there are folders dedicated to
contain scripts to execute while suspend/resume (just like init.d
This probably isn't exactly what you're looking for, but...
I believe /etc/enlightenment/suspend.sh is the file ran to cause the
suspend. You could modify that. I don't know if there's an
equivalent for resume.
no enlightment here, so no go.
That suspend script uses FSO. And it seems
I don't remember exactly where, but there are folders dedicated to
contain scripts to execute while suspend/resume (just like init.d).
yes, below /etc/apm/ -- but that requires a running apm, which is quite an
overhead for that simple task
is there any infrastructure to run scripts upon suspend resp resume?
the only way so far seems to be using apmd -- but that adds considerable
delay to resume ...
___
Openmoko community mailing list
community@lists.openmoko.org
26, 2009 at 4:31 PM, Florian Hackenberger
f.hackenber...@chello.at wrote:
On Thursday 26 February 2009 18:08:54 Marco Trevisan (Treviño)
wrote:
Check your uboot commandline loglevel value... It highly
impacts on the
suspend/resume time. I've set it to 3
On Thu, 2009-02-26 at 22:31 +0100, Florian Hackenberger wrote:
On Thursday 26 February 2009 18:08:54 Marco Trevisan (Treviño) wrote:
Check your uboot commandline loglevel value... It highly impacts on the
suspend/resume time. I've set it to 3 (but some time ago was set by the
system to 8
On Fri, 2009-02-27 at 17:20 +0900, W.Kenworthy wrote:
On Thu, 2009-02-26 at 22:31 +0100, Florian Hackenberger wrote:
On Thursday 26 February 2009 18:08:54 Marco Trevisan (Treviño) wrote:
Check your uboot commandline loglevel value... It highly impacts on the
suspend/resume time. I've set
Michael 'Mickey' Lauer wrote:
I don't think that they simply disable the backlight. Resuming from SHR
unstable takes about 5-6 seconds (no incoming call), while 2008.12 resumes
under 3 seconds. While this is not a scientific measurement, 2008.12 surely
is a lot faster. Any other ideas what
timestamping enabled, maybe the dmesg
during suspend / resume has a hint if it's something on the kernel side.
- -Andy
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iEYEARECAAYFAkmmlxoACgkQOjLpvpq7dMptXwCdH85IfZksSKJyDQ6u5Akk4T7p
on the
suspend/resume time. I've set it to 3 (but some time ago was set by the
system to 8, and I had to wait more than 6-7 seconds to wake the phone,
while it generally takes just 1-2 secs).
Those commands in the uBoot shell should do the work:
setenv bootargs roofstype=ext2 root=/dev/mmcblk0p2 console=tty0
.
Check your uboot commandline loglevel value... It highly impacts on the
suspend/resume time. I've set it to 3 (but some time ago was set by the
system to 8, and I had to wait more than 6-7 seconds to wake the phone,
while it generally takes just 1-2 secs).
Those commands in the uBoot shell
To the List,
When I tapped the power button in previous versions, I was presented
with a window offering buttons to suspend, lock, shutdown, etc, same
as then I click the 'X' button in the shelf while at the home screen.
In current versions, a tap of the power button brings up this menu and
drops
Upgrade, suspend on power is removed on latest shr-unstable (it is for
few days :P)
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Hrm, I just did that at lunch to no avail. Do I have to reflash or
should opkg update/upgrade be enough?
On Thu, Feb 26, 2009 at 3:01 PM, Johny Tenfinger seba.d...@gmail.com wrote:
Upgrade, suspend on power is removed on latest shr-unstable (it is for
few days :P)
opkg update/upgrade should be enough. You can manually edit
/etc/freesmartphone/oevents/rules.yaml too.
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
On Thursday 26 February 2009 18:08:54 Marco Trevisan (Treviño) wrote:
Check your uboot commandline loglevel value... It highly impacts on the
suspend/resume time. I've set it to 3 (but some time ago was set by the
system to 8, and I had to wait more than 6-7 seconds to wake the phone,
while
...
Warren
On Thu, Feb 26, 2009 at 4:31 PM, Florian Hackenberger
f.hackenber...@chello.at wrote:
On Thursday 26 February 2009 18:08:54 Marco Trevisan (Treviño) wrote:
Check your uboot commandline loglevel value... It highly impacts on the
suspend/resume time. I've set it to 3 (but some time ago
with
suspend/resume problems in the past and only will do that once it proves
100% solid.
I don't think that they simply disable the backlight. Resuming from SHR
unstable takes about 5-6 seconds (no incoming call), while 2008.12 resumes
under 3 seconds. While this is not a scientific measurement
Are you booting from NAND or NOR flash? I know when I boot from NAND
flash I see a bunch of text scroll by on resume. I don't see that
when booted from NOR. I don't know why... Have you tried that?
-Steven
On Mon, Feb 23, 2009 at 2:32 AM, Florian Hackenberger
f.hackenber...@chello.at wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Are you booting from NAND or NOR flash? I know when I boot from NAND
| flash I see a bunch of text scroll by on resume. I don't see that
| when booted from NOR. I don't know why... Have you tried that?
Hi!
I noticed that suspending / resuming on 2008.12 is quite fast compared
to SHR. The difference which is most noticeable is that SHR switches to
a virtual terminal before and right after suspending, as opposed to
2008.12 which resumes right into X. Is there a way to replicate this
behaviour
Florian Hackenberger f.hackenber...@chello.at writes:
behaviour on SHR? I suspect that we could save at least a second of
Are you sure? To me it seemed that 2008.12 just turned the backlight
on only when you were already in X?
___
Openmoko community
which resumes right into X.
Chances are they just cover up by turning backlight off prior to doing
real suspend and then wait until resume has happened before turning it
on again. We're not doing this yet, since we had our share with
suspend/resume problems in the past and only will do that once
for userspace to be adapted to test the suspend/resume
functionality (on FSO, only frameworkd?).
frameworkd newer than 31 Dec should properly support both kernels. I'm
afraid it's not included in any images yet (please correct me if i am
wrong).
Latest fso-frameworkd in debian is 0.8.4.3
as well.
I only care for userspace to be adapted to test the suspend/resume
functionality (on FSO, only frameworkd?).
frameworkd newer than 31 Dec should properly support both kernels. I'm
afraid it's not included in any images yet (please correct me if i am
wrong).
Latest fso-frameworkd
Hi,
Fox Mulder quakem...@gmx.net writes:
Actually, you can try to change from 2.6.24 after applying an ad-hoc
patch from http://trac.freesmartphone.org/ticket/293 even on old
version that's provided by Debian (that's exactly what i did a month ago).
Ok.
I downloaded the fso-frameworkd
Paul Fertser wrote:
Hi,
Fox Mulder quakem...@gmx.net writes:
Actually, you can try to change from 2.6.24 after applying an ad-hoc
patch from http://trac.freesmartphone.org/ticket/293 even on old
version that's provided by Debian (that's exactly what i did a month ago).
Ok.
I downloaded
Fox Mulder wrote:
Paul Fertser wrote:
Hi,
Fox Mulder quakem...@gmx.net writes:
Actually, you can try to change from 2.6.24 after applying an ad-hoc
patch from http://trac.freesmartphone.org/ticket/293 even on old
version that's provided by Debian (that's exactly what i did a month ago).
Hi,
Fox Mulder quakem...@gmx.net writes:
I installed the om toolchain and compiled the 2.6.28 kernel after some
help of [1] and google with ./build dummy. After i compiled the kernel
i got dummy/uImage-GTA02.bin what looks quite good so far.
But how do i extract the compiled modules from the
Paul Fertser wrote:
Hi,
Fox Mulder quakem...@gmx.net writes:
I installed the om toolchain and compiled the 2.6.28 kernel after some
help of [1] and google with ./build dummy. After i compiled the kernel
i got dummy/uImage-GTA02.bin what looks quite good so far.
But how do i extract the
Fox Mulder quakem...@gmx.net writes:
Could it be that i have to issue some command which produces the modules
tar.gz file?
Oh, man... If you don't want to read ``build'' then please do it by
hand in the root of the build:
rm -rf staging
mkdir -p staging
make ARCH=arm modules_install
On Monday 05 January 2009 15:29:54 Fox Mulder wrote:
If you give me a hint how to activate this feature i will try it. But i
have to say that most times i tried suspend zhone was not running and
therefore my gsm wasn't activated.
On /etc/frameworkd.conf
[ogsmd]
ti_calypso_deep_sleep = never
On Monday 05 January 2009 14:45:26 Fox Mulder wrote:
Hi all,
many mails i read in the kernel mailing list show that newer patches
should only be applied to andy-tracking kernel and no more to the old
2.6.24 om kernel.
I forgot to say
Please, try it and let us know if it solves also your
Hi all,
many mails i read in the kernel mailing list show that newer patches
should only be applied to andy-tracking kernel and no more to the old
2.6.24 om kernel.
Especially the suspend/resume behaviour seems to be a big problem with
the 2.6.24 kernel. I install about once a week a new 2.6.24
as well.
I only care for userspace to be adapted to test the suspend/resume
functionality (on FSO, only frameworkd?).
If one of the devs could give some pointers on what should change I can have a
go at it :)
grtz,
Sander
___
Openmoko community mailing
David Garabana Barro wrote:
On Monday 05 January 2009 14:45:26 Fox Mulder wrote:
Hi all,
many mails i read in the kernel mailing list show that newer patches
should only be applied to andy-tracking kernel and no more to the old
2.6.24 om kernel.
I forgot to say
Please, try it and let
On Monday 05 January 2009 14:45:26 Fox Mulder wrote:
Hi all,
many mails i read in the kernel mailing list show that newer patches
should only be applied to andy-tracking kernel and no more to the old
2.6.24 om kernel.
Especially the suspend/resume behaviour seems to be a big problem
Hi,
Sander van Grieken san...@3v8.net writes:
So the question is, when will the default kernel be replaced by the new
2.6.28 andy kernel so that userspace tools could be adapted to it?
That would be my question as well.
I only care for userspace to be adapted to test the suspend/resume
I have no SIM inserted so it should not be a Calypso problem.
i am not sure if simply not inserting a sim completely disables the
calypso. in fact, from my limited understanding of the issue and the
little that is left month later i can imagine scenarios where not having a
sim inserted
* Fox Mulder quakem...@gmx.net [090105 15:34]:
David Garabana Barro wrote:
On Monday 05 January 2009 14:45:26 Fox Mulder wrote:
Hi all,
many mails i read in the kernel mailing list show that newer patches
should only be applied to andy-tracking kernel and no more to the old
2.6.24 om
the suspend/resume
functionality (on FSO, only frameworkd?).
frameworkd newer than 31 Dec should properly support both kernels. I'm
afraid it's not included in any images yet (please correct me if i am wrong).
Latest fso-frameworkd in debian is 0.8.4.3-20081215-1 which is older
than 31 dec i
for userspace to be adapted to test the suspend/resume
functionality (on FSO, only frameworkd?).
frameworkd newer than 31 Dec should properly support both kernels. I'm
afraid it's not included in any images yet (please correct me if i am wrong).
Latest fso-frameworkd in debian is 0.8.4.3
Fox Mulder quakem...@gmx.net writes:
That's not good.
Is there another way to get the wlan status with help of a console
command like dbus or anything else?
I am not sure. There's an ioctl but it seems to give different results
than the power_on sysfs node.
Hi,
Timo Juhani Lindfors timo.lindf...@iki.fi writes:
That's not good.
Is there another way to get the wlan status with help of a console
command like dbus or anything else?
I am not sure. There's an ioctl but it seems to give different results
than the power_on sysfs node.
It was recently
Paul Fertser fercer...@gmail.com writes:
echo s3c2440-sdi /sys/bus/platform/devices/s3c2440-sdi/driver/unbind
Aha, so this should reduce power consumption?
___
Openmoko community mailing list
community@lists.openmoko.org
Hi,
Timo Juhani Lindfors timo.lindf...@iki.fi writes:
Paul Fertser fercer...@gmail.com writes:
echo s3c2440-sdi /sys/bus/platform/devices/s3c2440-sdi/driver/unbind
Aha, so this should reduce power consumption?
As far as i understand it is as effective as sending the magic ioctl
and equally
.
If there is more than one power state for the wlan module i want to log
the exact state instead of 0/1, but where to get it?
And another problem i have is that after the last ~10 hour
suspend/resume cycle the process events/0 consumes ~25% cpu power
constantly. I don't know what to do against this problem
Fox Mulder quakem...@gmx.net writes:
My problem now is, that i can't find any suitable file for wlan. I only
Which kernel? andy-tracking de473 has one for wlan too.
Btw, I have a similar script too. It tells me how many percentage
units of capacity per hour were lost during suspend when the
Timo Juhani Lindfors wrote:
Fox Mulder quakem...@gmx.net writes:
My problem now is, that i can't find any suitable file for wlan. I only
Which kernel? andy-tracking de473 has one for wlan too.
Btw, I have a similar script too. It tells me how many percentage
units of capacity per hour
Hi!
How to determine the event/device (alarm/incoming call/sms/power button
etc.) that resumed a suspended Freerunner?
Regards
Nicola
___
Openmoko community mailing list
community@lists.openmoko.org
2008/11/1 Robin Paulson [EMAIL PROTECTED]
2008/11/2 Nicola Mfb [EMAIL PROTECTED]:
How to determine the event/device (alarm/incoming call/sms/power button
etc.) that resumed a suspended Freerunner?
http://wiki.openmoko.org/wiki/GTA02_sysfs#Resume_Reason
Great!
I was searching without
On Tue, 2008-08-26 at 18:38 +0200, AVee wrote:
Depending on your usage of the SD card you could also workaround the issue
with a few symlinks. When the card is wrongly mounted just add symlinks to
the new location of the content of the card in /media/card/. Once you did
that /media/card
Is it possible to execute some script every time the neo comes out from
suspend only once?
I would like to suspend it with a manually script which enables the
sd_idleclk, syncs the sd-card, waits a few seconds and then go to sleep.
But after resume i want to disable sd_idleclk automatically so
Simon Matthews wrote:
I
would be interested to know if anyone else has tried it and if it works
for them.
Works for me. Two shell scripts:
/etc/apm/suspend.d/00sd_idleclk
which contains
That is exactly the thing i was searching for. Scripts that would be
automatically executed before suspend or after resume. :)
Now i will try this and activate suspend support on my neo. Until now i
don't use suspend with my debian system on the sd-card because i don't
want to have problems with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
here another workaround i worked out this evening:
first i turned off apmd - when running it prevents system from
suspending - more investigation going on
what's actually running for me is:
mv /usr/bin/apm /usr/bin/apm.o
creating /usr/bin/apm with
With my 8G Sandisk SD card, i can reliably fix the problems i have been
having by turning on the SD clock all the time. To do this type the
command
echo 1 /sys/module/glamo_mci/parameters/sd_idleclk
then do something that will access the SD card before doing a suspend.
This of course won't do
This of course won't do the GPS much good, but i think the real fix
might be to give the SD card more clock cycles before and after commands
to give it time to finish executing commands.
wouldn't it be sensible to turn on the sd clock before suspend and do
somthing? after resume the clock
Maybe it is possible to get a workaround for this problem until it is
fixed. When using a custom suspend script we maybe could do this stuff
manual.
When i would suspend the neo i start a script which first activates the
sd_idleclk. Than it activates some access to the sd card and after that
Will do, the only problem is that I don't know how to suspend/resume in
2007.2. Wasn't it a terminal command, or something to that effect?
apm -s
or
echo mem /sys/power/state
___
Openmoko community mailing list
community@lists.openmoko.org
http
Between attempts did you erase and reflash both the kernel and rootfs as
well as remove all power
for 30seconds (battery and usb) to completely reset the phone?
Ben
Robert Bieber wrote:
When OM2008.8 was released, I flashed it to my Freerunner, and suspend
and resume worked impeccably for
known software bug - try 2007.2 which doesnt have it.
BillK
On Sat, 2008-08-16 at 11:41 -0400, Robert Bieber wrote:
When OM2008.8 was released, I flashed it to my Freerunner, and suspend
and resume worked impeccably for the first couple of days I had it.
After that, however, it started
The problem isn't just occurring in 2008.8, the same happens in FSO and
Qtopia. If it were a software issue, it would seem that reflashing
would at least have it working as long as it worked in the first place,
but I now have no ability to come out of suspend at all, even after
flashing the
AFAIK they all use the same kernel. Look for a file called resume reason.
-Nick
Robert Bieber wrote:
The problem isn't just occurring in 2008.8, the same happens in FSO and
Qtopia. If it were a software issue, it would seem that reflashing
would at least have it working as long as it
FSO, 2008.8 and to some extent qtopia share a lot of code. Try 2007.2
while you are flashing things.
BillK
On Sun, 2008-08-17 at 00:39 -0400, Robert Bieber wrote:
The problem isn't just occurring in 2008.8, the same happens in FSO and
Qtopia. If it were a software issue, it would seem that
Will do, the only problem is that I don't know how to suspend/resume in
2007.2. Wasn't it a terminal command, or something to that effect?
William Kenworthy wrote:
FSO, 2008.8 and to some extent qtopia share a lot of code. Try 2007.2
while you are flashing things.
BillK
On Sun, 2008-08
On Wed, Jul 30, 2008 at 04:42:52PM -0400, Matthew Lane wrote:
When suspending, GSM calls DO wake the phone up, but SMS does not?
Also, when I resume from a suspend, I cannot send/receive SMS? Qtopia
also seems to have this problem..once I suspend I cannot receive SMS,
and I'm not even
was
wondering if my problems are common as I cannot find any documentation
on suspend/resume in the wiki, and not particular answers to my
questions in previous discussions on the mailing list.
When suspending, GSM calls DO wake the phone up, but SMS does not?
Also, when I resume from a suspend, I cannot
documentation
on suspend/resume in the wiki, and not particular answers to my
questions in previous discussions on the mailing list.
When suspending, GSM calls DO wake the phone up, but SMS does not?
Also, when I resume from a suspend, I cannot send/receive SMS? Qtopia
also seems to have
been some bugs with it and it's not entirely finished, but I was
wondering if my problems are common as I cannot find any documentation
on suspend/resume in the wiki, and not particular answers to my
questions in previous discussions on the mailing list.
When suspending, GSM calls DO wake
in the past there have
been some bugs with it and it's not entirely finished, but I was
wondering if my problems are common as I cannot find any documentation
on suspend/resume in the wiki, and not particular answers to my
questions in previous discussions on the mailing list.
When suspending
81 matches
Mail list logo
