Re: [SHR-Today] Accept call without unlocking
The reason for downgrading is simple - 2.6.29 doesnt work for gsm - the error is similar to the one reported for GPS (rxerr) a while back. I just flashed uboot back over qi - no wsod yet, tough need a few more resumes to be sure. Paul F. has worked with me on on it at one point - his take is I have a faulty GSM chip - my thoughts are that it works with certain combinations, not others which means to me something is not being handled correctly. There were a lot of changes in handling serial ports between 2.6.28 and 2.6.29 - I am slowly going over them in order to see whats changed in regard to getting GSM operating. BillK On Tue, 2009-09-08 at 16:29 +0200, Sebastian Krzyszkowiak wrote: > On 9/8/09, Jens Seidel wrote: > > On Tue, Sep 08, 2009 at 08:56:07AM +0800, William Kenworthy wrote: > >> On Mon, 2009-09-07 at 16:43 +0200, Sebastian Krzyszkowiak wrote: > >> > WTF? WSOD still happening? What kernel do you use? o_O > >> > >> 2.6.28 - never been able to get GSM working on 2.6.29 so thats not an > >> option. > >> > >> WSOD happens when using Qi, not when using uboot. But uboot may need > >> multiple boot attempts before even 2.6.28 will talk to the gsm chipset, > >> whereas Qi is reliable - something is not getting initialised properly > >> somewhere. > > > > Funny, it's opposite for me. I used until yesterday 2.6.29 together with > > uboot but switched back to 2.6.28 and now the WSOD vanished. Great! > > > > With 2.6.29 WSOD happened very often (I would say in 50% of all cases). > > Don't remember GSM status with 2.6.29 (works great with 2.6.28), used it > > in the past mainly as PDA. > > > > Jens > > BTW. Why are you playing with kernels instead of using ditribution > one? I understand playing with 2.6.31 RC kernels, but downgrading? > SHR-unstable comes with latest andy-tracking. If something doesn't > work in this kernel, then it has to be reported, debuged and fixed, > instead of just switching back and being quiet about that! > -- William Kenworthy Home in Perth! ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR-Today] Accept call without unlocking
On 9/8/09, William Kenworthy wrote: > On Mon, 2009-09-07 at 16:43 +0200, Sebastian Krzyszkowiak wrote: >> On 9/7/09, William Kenworthy wrote: >> > On Mon, 2009-09-07 at 17:20 +0530, Vikas Saurabh wrote: >> >> Hi, >> >> >> >> Quite often when I get a call, all I see is the locked screen. Now, >> >> what I would expect is to able to accept the call without actually >> >> unlocking the phone. >> >> Can we have another slider like control with slider thumb in between. >> >> Moving the slide to left accepts the call and moving it to the right >> >> rejects it. >> >> >> >> --Vikas >> >> >> >> PS: I had a look at the TODO list in git( >> >> http://github.com/slyon/today/blob/b279a6af85352de0ca9db4ac3c1f4f06e086ed8b/TODO) >> >> and this didn't appear there >> >> >> > >> > An observation - Ive lost a few calls (~5) now due to wsod on resume - >> > until this is fixed (and after so long, is it likely to ever be fixed?) >> >> WTF? WSOD still happening? What kernel do you use? o_O >> > > 2.6.28 - never been able to get GSM working on 2.6.29 so thats not an > option. > > WSOD happens when using Qi, not when using uboot. But uboot may need > multiple boot attempts before even 2.6.28 will talk to the gsm chipset, > whereas Qi is reliable - something is not getting initialised properly > somewhere. > > Yeah, I know I should be using 2.6.29, but I dont think thats the > problem, and I if I cant use it as a phone whats the point? > > BillK WTF? 2.6.29 is shipped by default in SHR, and it obviously should work. And the point is - to debug and fix it, as it's supposed to work and 2.6.28 is now deprecated :P Upgrade bootloader, kernel and rootfs. It definitely has to work. -- Sebastian Krzyszkowiak dos ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: WSOD (Was: Re: [SHR-Today] Accept call without unlocking)
On 9/8/09, Jens Seidel wrote: > On Tue, Sep 08, 2009 at 04:29:19PM +0200, Sebastian Krzyszkowiak wrote: >> On 9/8/09, Jens Seidel wrote: >> > Funny, it's opposite for me. I used until yesterday 2.6.29 together with >> > uboot but switched back to 2.6.28 and now the WSOD vanished. Great! >> > >> > With 2.6.29 WSOD happened very often (I would say in 50% of all cases). >> > Don't remember GSM status with 2.6.29 (works great with 2.6.28), used it >> > in the past mainly as PDA. >> >> BTW. Why are you playing with kernels instead of using ditribution >> one? > > A good question and I don't know the proper answer. I use SHR but have also > Debian installed. SHR is currently more stable and much fancier so I prefer > it. I often update the system via opkg update and opkg upgrade which > resulted > in kernel 2.6.29-rc3. > > Why should I keep it if it is unstable? And a very stupid question: I know > that 2.6.29-rc3 is installed in the file system (/boot) but is it used or > the kernel in /dev/mtdblock3? I didn't found the answer in the SHR manual > and wasted yesterday at least 3 hours because of it. I also checked the > uboot config, booted via USB serial connection started printenv, ... > That's not a easy way!!! I flashed finally directly into the "kernel" > partition which seems to work. So opkg doesn't affect the running kernel ... > > I know that Debian provided a script to customize the uboot configuration > and I know that the kernel in the filesystem is used and /dev/mtdblock3 > as fallback (or in reverse order, don't remember). But SHR? > > Digging into the Wiki and mailinglist postings is still the most time > consuming task and I'm always lost in it and not able to do any work with > my phone! > >> I understand playing with 2.6.31 RC kernels, but downgrading? > > I prefer a WSOD free kernel, you not? > >> SHR-unstable comes with latest andy-tracking. If something doesn't >> work in this kernel, then it has to be reported, debuged and fixed, >> instead of just switching back and being quiet about that! > > The problem in 2.6.29 is already known, there is no need to report it > so I tried to avoid it using 2.6.28 (which reports itself as > 2.6.29 :-)). If the latest andy-tracking kernel is no longer affected why > aren't both WSOD bug reports updated? I wasn't even aware until very > recently that the original WSOD bug was fixed as the initial report is still > open without activity since months. > > I now tried again at least ten minutes to find the SHR kernel download link > but failed, it's not on http://wiki.openmoko.org/wiki/Download, > http://wiki.openmoko.org/wiki/Flashing#Flashing_the_Kernel, > http://wiki.openmoko.org/wiki/SHR_User_Manual, wasn't able to find it via > Google, What a mess! At least I don't remember seeing anything andy-tracking > related (except the Wiki article about getting the source). > > Jens Kernel is in images and in repositiories. After opkg upgrade at /boot/uImage-GTA02 you should have latest kernel (even if it wasn't flashed by opkg) which you should use to flash if you want to test it. That kernel is supposed to be quite stable and usable. -- Sebastian Krzyszkowiak dos ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
WSOD (Was: Re: [SHR-Today] Accept call without unlocking)
On Tue, Sep 08, 2009 at 04:29:19PM +0200, Sebastian Krzyszkowiak wrote: > On 9/8/09, Jens Seidel wrote: > > Funny, it's opposite for me. I used until yesterday 2.6.29 together with > > uboot but switched back to 2.6.28 and now the WSOD vanished. Great! > > > > With 2.6.29 WSOD happened very often (I would say in 50% of all cases). > > Don't remember GSM status with 2.6.29 (works great with 2.6.28), used it > > in the past mainly as PDA. > > BTW. Why are you playing with kernels instead of using ditribution > one? A good question and I don't know the proper answer. I use SHR but have also Debian installed. SHR is currently more stable and much fancier so I prefer it. I often update the system via opkg update and opkg upgrade which resulted in kernel 2.6.29-rc3. Why should I keep it if it is unstable? And a very stupid question: I know that 2.6.29-rc3 is installed in the file system (/boot) but is it used or the kernel in /dev/mtdblock3? I didn't found the answer in the SHR manual and wasted yesterday at least 3 hours because of it. I also checked the uboot config, booted via USB serial connection started printenv, ... That's not a easy way!!! I flashed finally directly into the "kernel" partition which seems to work. So opkg doesn't affect the running kernel ... I know that Debian provided a script to customize the uboot configuration and I know that the kernel in the filesystem is used and /dev/mtdblock3 as fallback (or in reverse order, don't remember). But SHR? Digging into the Wiki and mailinglist postings is still the most time consuming task and I'm always lost in it and not able to do any work with my phone! > I understand playing with 2.6.31 RC kernels, but downgrading? I prefer a WSOD free kernel, you not? > SHR-unstable comes with latest andy-tracking. If something doesn't > work in this kernel, then it has to be reported, debuged and fixed, > instead of just switching back and being quiet about that! The problem in 2.6.29 is already known, there is no need to report it so I tried to avoid it using 2.6.28 (which reports itself as 2.6.29 :-)). If the latest andy-tracking kernel is no longer affected why aren't both WSOD bug reports updated? I wasn't even aware until very recently that the original WSOD bug was fixed as the initial report is still open without activity since months. I now tried again at least ten minutes to find the SHR kernel download link but failed, it's not on http://wiki.openmoko.org/wiki/Download, http://wiki.openmoko.org/wiki/Flashing#Flashing_the_Kernel, http://wiki.openmoko.org/wiki/SHR_User_Manual, wasn't able to find it via Google, What a mess! At least I don't remember seeing anything andy-tracking related (except the Wiki article about getting the source). Jens ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR-Today] Accept call without unlocking
On 9/8/09, Jens Seidel wrote: > On Tue, Sep 08, 2009 at 08:56:07AM +0800, William Kenworthy wrote: >> On Mon, 2009-09-07 at 16:43 +0200, Sebastian Krzyszkowiak wrote: >> > WTF? WSOD still happening? What kernel do you use? o_O >> >> 2.6.28 - never been able to get GSM working on 2.6.29 so thats not an >> option. >> >> WSOD happens when using Qi, not when using uboot. But uboot may need >> multiple boot attempts before even 2.6.28 will talk to the gsm chipset, >> whereas Qi is reliable - something is not getting initialised properly >> somewhere. > > Funny, it's opposite for me. I used until yesterday 2.6.29 together with > uboot but switched back to 2.6.28 and now the WSOD vanished. Great! > > With 2.6.29 WSOD happened very often (I would say in 50% of all cases). > Don't remember GSM status with 2.6.29 (works great with 2.6.28), used it > in the past mainly as PDA. > > Jens BTW. Why are you playing with kernels instead of using ditribution one? I understand playing with 2.6.31 RC kernels, but downgrading? SHR-unstable comes with latest andy-tracking. If something doesn't work in this kernel, then it has to be reported, debuged and fixed, instead of just switching back and being quiet about that! -- Sebastian Krzyszkowiak dos ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR-Today] Accept call without unlocking
On Tue, Sep 08, 2009 at 08:56:07AM +0800, William Kenworthy wrote: > On Mon, 2009-09-07 at 16:43 +0200, Sebastian Krzyszkowiak wrote: > > WTF? WSOD still happening? What kernel do you use? o_O > > 2.6.28 - never been able to get GSM working on 2.6.29 so thats not an > option. > > WSOD happens when using Qi, not when using uboot. But uboot may need > multiple boot attempts before even 2.6.28 will talk to the gsm chipset, > whereas Qi is reliable - something is not getting initialised properly > somewhere. Funny, it's opposite for me. I used until yesterday 2.6.29 together with uboot but switched back to 2.6.28 and now the WSOD vanished. Great! With 2.6.29 WSOD happened very often (I would say in 50% of all cases). Don't remember GSM status with 2.6.29 (works great with 2.6.28), used it in the past mainly as PDA. Jens ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR-Today] Accept call without unlocking
On Tuesday 08 September 2009 05:34, undrwater wrote: > Vikas Saurabh wrote: > > Can we have another slider like control with slider thumb in between. > > Moving the slide to left accepts the call and moving it to the right > > rejects it. > > I like the idea as well. Doesn't have to be a slider, but a definite pair > of gestures could works as well. I like the Z movement from the Zlock program. To me, this is a much simpler movement that can more easily be done without looking at the screen. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR-Today] Accept call without unlocking
Vikas Saurabh wrote: > > > Can we have another slider like control with slider thumb in between. > Moving the slide to left accepts the call and moving it to the right > rejects it. > > I like the idea as well. Doesn't have to be a slider, but a definite pair of gestures could works as well. russell dwiggins -- View this message in context: http://n2.nabble.com/SHR-Today-Accept-call-without-unlocking-tp3596892p3600813.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR-Today] Accept call without unlocking
On Mon, 2009-09-07 at 16:54 +0200, Jens Seidel wrote: > On Mon, Sep 07, 2009 at 04:43:59PM +0200, Sebastian Krzyszkowiak wrote: > > On 9/7/09, William Kenworthy wrote: > > > An observation - Ive lost a few calls (~5) now due to wsod on resume - > > > until this is fixed (and after so long, is it likely to ever be fixed?) > > > > WTF? WSOD still happening? What kernel do you use? o_O > > Oh, yes, WSOD still happens. > > But in contrast to the past the problem may vanish after a further suspend, > see http://docs.openmoko.org/trac/ticket/2274 (Kernel regression: white > screen of death reappeared with 2.6.29). > > I was suprised about the fact that one no longer has to restart to get again > a working state and verified it only a few hours ago. In general one needs > only one or two suspend iterations until the white screen vanished :-) > > Jens > Yes, suspending fixes it tempoarily - it will randomly come back. And suspending when a call comes in is not really what you want. WSOD happens randomly (maybe 1 in 10) on anything that causes the FR to come out of suspend, manual, sms, call, alarm, ... BillK ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR-Today] Accept call without unlocking
On Mon, 2009-09-07 at 16:43 +0200, Sebastian Krzyszkowiak wrote: > On 9/7/09, William Kenworthy wrote: > > On Mon, 2009-09-07 at 17:20 +0530, Vikas Saurabh wrote: > >> Hi, > >> > >> Quite often when I get a call, all I see is the locked screen. Now, > >> what I would expect is to able to accept the call without actually > >> unlocking the phone. > >> Can we have another slider like control with slider thumb in between. > >> Moving the slide to left accepts the call and moving it to the right > >> rejects it. > >> > >> --Vikas > >> > >> PS: I had a look at the TODO list in git( > >> http://github.com/slyon/today/blob/b279a6af85352de0ca9db4ac3c1f4f06e086ed8b/TODO) > >> and this didn't appear there > >> > > > > An observation - Ive lost a few calls (~5) now due to wsod on resume - > > until this is fixed (and after so long, is it likely to ever be fixed?) > > WTF? WSOD still happening? What kernel do you use? o_O > 2.6.28 - never been able to get GSM working on 2.6.29 so thats not an option. WSOD happens when using Qi, not when using uboot. But uboot may need multiple boot attempts before even 2.6.28 will talk to the gsm chipset, whereas Qi is reliable - something is not getting initialised properly somewhere. Yeah, I know I should be using 2.6.29, but I dont think thats the problem, and I if I cant use it as a phone whats the point? BillK ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR-Today] Accept call without unlocking
On Mon, Sep 07, 2009 at 04:43:59PM +0200, Sebastian Krzyszkowiak wrote: > On 9/7/09, William Kenworthy wrote: > > An observation - Ive lost a few calls (~5) now due to wsod on resume - > > until this is fixed (and after so long, is it likely to ever be fixed?) > > WTF? WSOD still happening? What kernel do you use? o_O Oh, yes, WSOD still happens. But in contrast to the past the problem may vanish after a further suspend, see http://docs.openmoko.org/trac/ticket/2274 (Kernel regression: white screen of death reappeared with 2.6.29). I was suprised about the fact that one no longer has to restart to get again a working state and verified it only a few hours ago. In general one needs only one or two suspend iterations until the white screen vanished :-) Jens ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR-Today] Accept call without unlocking
On Monday 07 September 2009 07:50:30 am Vikas Saurabh wrote:
> Hi,
>
> Quite often when I get a call, all I see is the locked screen. Now,
> what I would expect is to able to accept the call without actually
> unlocking the phone.
> Can we have another slider like control with slider thumb in between.
> Moving the slide to left accepts the call and moving it to the right
> rejects it.
>
I like the slider idea, then we can avoid the same problem that the iphone
users have, pocket answering/rejecting. One of my friends has a iphone and
that is one thing he doesn't like when he gets a call a window opens up above
the home ("lock") screen saying who is calling and has a button to answer or
to reject the call. The problem he has is accidentally hitting one of the two
but tens trying to get his phone out of his pocket. A slider should help
prevent/reduce this problem.
--
"We must plan for freedom, and not only for security, if for no other reason
than only freedom can make security more secure." Karl Popper
signature.asc
Description: This is a digitally signed message part.
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR-Today] Accept call without unlocking
> An observation - Ive lost a few calls (~5) now due to wsod on resume - > until this is fixed (and after so long, is it likely to ever be fixed?) > - making the bottom left 1/4 of shr-today accept, and bottom right > quarter reject would be nice when the thing wsods on resume (the TS > still works - just cant see what you are doing) when a call comes in. > Yes its a hack, but unless wsod is fixed, what alternative do we have. is there a way to detect wsod from software at all? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR-Today] Accept call without unlocking
On 9/7/09, William Kenworthy wrote: > On Mon, 2009-09-07 at 17:20 +0530, Vikas Saurabh wrote: >> Hi, >> >> Quite often when I get a call, all I see is the locked screen. Now, >> what I would expect is to able to accept the call without actually >> unlocking the phone. >> Can we have another slider like control with slider thumb in between. >> Moving the slide to left accepts the call and moving it to the right >> rejects it. >> >> --Vikas >> >> PS: I had a look at the TODO list in git( >> http://github.com/slyon/today/blob/b279a6af85352de0ca9db4ac3c1f4f06e086ed8b/TODO) >> and this didn't appear there >> > > An observation - Ive lost a few calls (~5) now due to wsod on resume - > until this is fixed (and after so long, is it likely to ever be fixed?) WTF? WSOD still happening? What kernel do you use? o_O -- Sebastian Krzyszkowiak dos ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR-Today] Accept call without unlocking
On Mon, 2009-09-07 at 17:20 +0530, Vikas Saurabh wrote: > Hi, > > Quite often when I get a call, all I see is the locked screen. Now, > what I would expect is to able to accept the call without actually > unlocking the phone. > Can we have another slider like control with slider thumb in between. > Moving the slide to left accepts the call and moving it to the right > rejects it. > > --Vikas > > PS: I had a look at the TODO list in git( > http://github.com/slyon/today/blob/b279a6af85352de0ca9db4ac3c1f4f06e086ed8b/TODO) > and this didn't appear there > An observation - Ive lost a few calls (~5) now due to wsod on resume - until this is fixed (and after so long, is it likely to ever be fixed?) - making the bottom left 1/4 of shr-today accept, and bottom right quarter reject would be nice when the thing wsods on resume (the TS still works - just cant see what you are doing) when a call comes in. Yes its a hack, but unless wsod is fixed, what alternative do we have. Oh, and sliders suck :) Got laughed at the other day when I dragged out the FR to look up a date - I had the screen brightness down a bit as I was previously using it indoors - finger operation of sliders isnt good (besides having to navigate layers of menus to get to it) - I might have laughed in frustration myself if I wasnt cringing from the derogatory comments the FR interface got - not a good advertisement :( BillK ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[SHR-Today] Accept call without unlocking
Hi, Quite often when I get a call, all I see is the locked screen. Now, what I would expect is to able to accept the call without actually unlocking the phone. Can we have another slider like control with slider thumb in between. Moving the slide to left accepts the call and moving it to the right rejects it. --Vikas PS: I had a look at the TODO list in git( http://github.com/slyon/today/blob/b279a6af85352de0ca9db4ac3c1f4f06e086ed8b/TODO) and this didn't appear there ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
