W.Kenworthy wrote:
Tried the NO_NEW_FAIR_SLEEPERS hack? - made a real difference to me on
this problem. To manually try it, mount debugfs and do the echo
command, or create as below and reboot.
In /etc/fstab add this line (all one line :)
debugfs /sys/kernel/debug
On Tue, 2009-10-20 at 12:10 +0200, Bernd Prünster wrote:
W.Kenworthy wrote:
Tried the NO_NEW_FAIR_SLEEPERS hack? - made a real difference to me on
this problem. To manually try it, mount debugfs and do the echo
command, or create as below and reboot.
In /etc/fstab add this line (all
William Kenworthy wrote:
I doubt its doing anything bad - seems more likely you have a
bad/misconfigured install, or possibly a bad/intermittant GSM modem
connection (the serial port side) as thats similar to what I see when it
doesnt initialise properly - lots of things in the framework do
William Kenworthy wrote:
...
I gave it another shot and i must say it quite awesome:
i called myself from another phone and the moment i heard it ringing my
fr woke up and showed the incoming call screen.
i know the debugfs approch might not be a nice and clean one, but i
couldn't care less
On Tue, 2009-10-20 at 15:33 +0200, Bernd Prünster wrote:
William Kenworthy wrote:
...
I gave it another shot and i must say it quite awesome:
i called myself from another phone and the moment i heard it ringing my
fr woke up and showed the incoming call screen.
i know the debugfs approch
2009/10/19 W.Kenworthy bi...@iinet.net.au
are you using the latest moko11 GSM firmware? - anything else and missed
messages are a distinct possibility.
http://wiki.openmoko.org/wiki/GSM/Flashing
BillK
Yes, I've updated the firmware. The missed calls are because I can't answer
them. I hit
Yes, I've updated the firmware. The missed calls are because I can't answer
them. I hit answer and the phone keeps ringing. The positive side is that I
know who called and can call back.
This happens to me on litephone...and I always thought that it was a
litephone issue. Which phone-app do
Am Montag, den 19.10.2009, 12:55 +0530 schrieb Vikas Saurabh:
Yes, I've updated the firmware. The missed calls are because I can't answer
them. I hit answer and the phone keeps ringing. The positive side is that I
know who called and can call back.
This happens to me on litephone...and I
2009/10/19 Vikas Saurabh vikas.saur...@gmail.com
Yes, I've updated the firmware. The missed calls are because I can't
answer
them. I hit answer and the phone keeps ringing. The positive side is that
I
know who called and can call back.
This happens to me on litephone...and I always
Tried the NO_NEW_FAIR_SLEEPERS hack? - made a real difference to me on
this problem. To manually try it, mount debugfs and do the echo
command, or create as below and reboot.
In /etc/fstab add this line (all one line :)
debugfs /sys/kernel/debug debugfs defaults
2009/10/19 W.Kenworthy bi...@iinet.net.au
debugfs exposes some knobs and innards of the kernel, the one here
making the kernels default scheduler behave more like the BFS scheduler
that hit the news a couple of months ago, creating a far more responsive
device including when it rings.
It's
On Mon, Oct 19, 2009 at 11:12:51AM +0800, W.Kenworthy wrote:
On Sun, 2009-10-18 at 21:46 +0100, Rui Miguel Silva Seabra wrote:
On Sun, Oct 18, 2009 at 08:49:02PM +0200, Michal Brzozowski wrote:
2009/10/18 Rui Miguel Silva Seabra r...@1407.org
I'm using SHR Unstable as a daily phone. Has
On Mon, 2009-10-19 at 10:56 +0200, Michal Brzozowski wrote:
2009/10/19 W.Kenworthy bi...@iinet.net.au
debugfs exposes some knobs and innards of the kernel, the one
here
making the kernels default scheduler behave more like the BFS
scheduler
that hit
So... what you guys are telling me is nothing has changed since the beginning
of september?
Is it at least faster than it was before? I remember everything would take
forever to load, even the terminal.
--
View this message in context:
http://n2.nabble.com/SHR-status-tp3845266p3855921.html
On Monday 19 October 2009 07:59:37 pm abatrour wrote:
So... what you guys are telling me is nothing has changed since the
beginning of september?
Is it at least faster than it was before? I remember everything would take
forever to load, even the terminal.
Well I have flashed the image
On Sun, Oct 18, 2009 at 11:01:15AM -0700, abatrour wrote:
I was wondering what the status of SHR is. I've been using android lately so
I am not caught up as to the progress of SHR.
I'm using SHR Unstable as a daily phone. Has quirks, but IMHO SHR Testing should
become what SHR Unstable is right
2009/10/18 Rui Miguel Silva Seabra r...@1407.org
I'm using SHR Unstable as a daily phone. Has quirks, but IMHO SHR Testing
should
become what SHR Unstable is right now before the next sync.
What date is your SHR-u from? I'm using one from August with some updates
and I miss phone calls from
On Sun, Oct 18, 2009 at 9:49 PM, Michal Brzozowski ruso...@poczta.fmwrote:
2009/10/18 Rui Miguel Silva Seabra r...@1407.org
I'm using SHR Unstable as a daily phone. Has quirks, but IMHO SHR Testing
should
become what SHR Unstable is right now before the next sync.
What date is your SHR-u
2009/10/18 Tony Berth tonybe...@googlemail.com:
On Sun, Oct 18, 2009 at 9:49 PM, Michal Brzozowski ruso...@poczta.fm
wrote:
What date is your SHR-u from? I'm using one from August with some updates
and I miss phone calls from time to time. Is there a new one that seems to
have reliable
On Sun, Oct 18, 2009 at 08:49:02PM +0200, Michal Brzozowski wrote:
2009/10/18 Rui Miguel Silva Seabra r...@1407.org
I'm using SHR Unstable as a daily phone. Has quirks, but IMHO SHR Testing
should
become what SHR Unstable is right now before the next sync.
What date is your SHR-u from?
8b48b1570910181149v43786743ue18d3346c1298...@mail.gmail.com
3494db260910181157p39cfadcv55ef478b934a8...@mail.gmail.com
Content-Type: text/plain; charset=Windows-1252
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
I'm using SHR Unstable as a daily phone. Has
On 10/18/09, Rui Miguel Silva Seabra r...@1407.org wrote:
On Sun, Oct 18, 2009 at 08:49:02PM +0200, Michal Brzozowski wrote:
2009/10/18 Rui Miguel Silva Seabra r...@1407.org
I'm using SHR Unstable as a daily phone. Has quirks, but IMHO SHR
Testing
should
become what SHR Unstable is right
I'm running a build from August but last upgraded on Sept 5th and it's
pretty stable. Had a few reports of bad audio quality, and a couple of
times where I've missed calls but it's fairly rare.
I spent a couple of weeks running the shr-testing candidate - which I
believe was basically a copy of
are you using the latest moko11 GSM firmware? - anything else and missed
messages are a distinct possibility.
http://wiki.openmoko.org/wiki/GSM/Flashing
BillK
On Sun, 2009-10-18 at 20:49 +0200, Michal Brzozowski wrote:
2009/10/18 Rui Miguel Silva Seabra r...@1407.org
I'm
On Sun, 2009-10-18 at 21:46 +0100, Rui Miguel Silva Seabra wrote:
On Sun, Oct 18, 2009 at 08:49:02PM +0200, Michal Brzozowski wrote:
2009/10/18 Rui Miguel Silva Seabra r...@1407.org
I'm using SHR Unstable as a daily phone. Has quirks, but IMHO SHR Testing
should
become what SHR
I have personally had many troubles with SHR in the past. For one, I
don't think the Contacts application has ever worked for my SIM card. It
immediately crashes. It might be because it hasn't finished loading all
of the contacts from SIM, but crashing is a poor way of handling this
issue.
One further hint - if you have any SD card problems, try slowing the SD
clock down and/or adjusting the drive for it. I have an otherwise
excellent 8G SD card (class 2 I think) that has to have the clock slowed
- if not I get all sorts of corruption and weird things happening - with
a slightly
27 matches
Mail list logo
