Getting escape,to work in om2007.2
I know there are alternative keyboards for the neo, however I prefer the original keyboard because of its easy customization to allow multi character input.Is there any way to get the escape to work on this distro so I am able to actualy use vi on it, without patching the distro? Thanx in advance _ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Om2008.9 suspend? - OM2007.2 battery life Om2008.9 battery life
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Timo Jyrinki wrote: 2008/10/1 Andy Green [EMAIL PROTECTED]: fixed this tonight on another tree and will update stable with it later or tomorrow. Just as a clarification, isn't the stable kernel tree only actually available in the unstable repository currently? Even testing has a kernel version from August (git a1e97c611), and the same version is in 2008.8 (stable) repository. Right -- I am talking about stable git branch for kernel itself. Currently updating of kernel in packaging is rather conservative... something I both approve of and am a bit dubious about at the same time. At least if folks can get at it from unstable it's OK, but I wonder what the deal is with mixing stable basis for the distro with cherrypicked kernel from unstable when it comes to module packages. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkjl2QIACgkQOjLpvpq7dMoJyACcDDJHyLxH6HxJpqfsJPK9Aro+ czMAn1TQ+YF9OrSRbmyKWqhG1odEAhE0 =aLSh -END PGP SIGNATURE- ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Om2008.9 suspend? - OM2007.2 battery life Om2008.9 battery life
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | if it is - you are victim of the qpe halted suspend before it ever got to the | kernel bug. ompower is stuck waiting for apm -s to return (indicating resume) | at which time it will turn the light back on. I guess I should have said if anything in userspace decides... then, but it is evidently the right idea. Just curious, what's qpe's POV about intercepting the suspend? I guess there are plans to have it not do it without a better reason? - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkjjLFYACgkQOjLpvpq7dMpXowCeNvH5dqvXRaCPtWrh8nlD/g3o ry0AniXta9j+dJ0ukIedgenCzULvlyXh =hHhe -END PGP SIGNATURE- ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Om2008.9 suspend? - OM2007.2 battery life Om2008.9 battery life
On Wed, 01 Oct 2008 08:53:02 +0100 Andy Green [EMAIL PROTECTED] babbled: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | if it is - you are victim of the qpe halted suspend before it ever got to the | kernel bug. ompower is stuck waiting for apm -s to return (indicating resume) | at which time it will turn the light back on. I guess I should have said if anything in userspace decides... then, but it is evidently the right idea. Just curious, what's qpe's POV about intercepting the suspend? I guess there are plans to have it not do it without a better reason? it needs to to tell the gsm modem to go into low power i'm suspended mode - thus it needs to intercept the suspend action until it's managed to do this. i THINK that qpe simply manages to error here. either calypso does the right thing and replies and qpe doesnt know, or calypso just errors or refuses. but the problem is definitely in that space somewhere. :( (kill the apm process thats hung and presto - backlight will be back on! but you have a badly behaving calypso i think... so ymmv after that) -- - Codito, ergo sum - I code, therefore I am -- The Rasterman (Carsten Haitzler)[EMAIL PROTECTED] ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Om2008.9 suspend? - OM2007.2 battery life Om2008.9 battery life
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | I was thinking of switching to the latest Om2008.9 from OM2007.2 | because Om2008.9 resumes a lot quicker from suspend. However, the | battery life with Om2008.9 is greatly reduced. This leads me to | believe that Om2008.9 either isn't truly suspending--more of a | standby--or just isn't suspending everything that OM2007.2 does. | Anyone else experiencing the same thing? | | The one difference is that Om2008.9 was running from the microsd card. | Would that make a difference as far as power usage during suspend? There's this new userspace power daemon that makes decisions about backlight and suspend now. If it decides to just keep backlight off for long periods, there's a bug in recent kernels that actually leaves the backlight slightly on (trying to avoid another bug in the PMU). I fixed this tonight on another tree and will update stable with it later or tomorrow. It might not be the whole story but it should help. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkjioNAACgkQOjLpvpq7dMpzdQCdH14VCgoAi0mwZdt3zNo/cXnd A3gAoIMKQmiYrZKE2FiGbwBG77gyntDC =DmKW -END PGP SIGNATURE- ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: OM2007.2
I would be curious to know what kind of developer numbers (non-OM employees) would provide support to a fork of OM2007.2 into a purely community driven project? I'll tag along if there is a fork. Does everyone think 2007 is a dead path and that the ASU/FSO course is the only one to follow? Not me! I witnessed all the work that went into OM 2007.2 over the last couple of years - including the days of OE - and when it was all chucked out for 'the new stuff' it was, frankly, a bit miserable. ; -- Jay Vaughan ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: OM2007.2
Lon, ASU will turn into OM 2008.8 Eventually FSO will turn into OM 2009 or so. From Openmoko's perspective, it's one 'stream' of images, and we care a lot about application compatibility. So for example for OM 2008.8, we want all OM 2007.2 apps to work. Like tangoGPS. We want it to be easy for anybody to remove Qtopia from 2008.8 completely, and bring the GTK+ based telephony apps back. Ideally just a few clicks in the Installer. Uninstall 'Qtopia', Install 'Poky'. Something like that. We are not there yet, but any help is appreciated and meanwhile we continue to work in that direction ourselves. Best Regards, Wolfgang On Jul 31, 2008, at 6:28 AM, Lon Lentz wrote: I would be curious to know what kind of developer numbers (non-OM employees) would provide support to a fork of OM2007.2 into a purely community driven project? Does everyone think 2007 is a dead path and that the ASU/FSO course is the only one to follow? On Sun, Jul 27, 2008 at 8:19 AM, Michael 'Mickey' Lauer [EMAIL PROTECTED] wrote: Openmoko does not actively develop OM2007.2, all resources are going into ASU (and the framework initiative). I think we should move to SHR once they have their first release. In the meantime, someone could/should drag all the Openmoko sources into a public Om project repository and continue developing 2007.2 there. If that's going to happen, ping me and I'll change the respective BitBake recipes in OE to pull from the new location. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: OM2007.2 continuously freezes!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | Andy Green wrote: | Someone was saying they will look at XGlamo and I don't think you're the | only one seeing some shakiness. | | Well, I'll use Xfbdev until there will be something of new in XGlamo or | in the kernel (about glamo itself). However I think I'll be moreover | limited! | | However, Andy, sure I'm not the only seeing these shakiness but I've not | read reports by someone that after few seconds of interface usage has | hangups and that on next reboot can't boot X (getting another freeze) | and that, again, can reboot it (without any stability by the way) only | after keeping the phone off few seconds. | | It's really hard to think that this is just a my software problem... If we talk about the same email, that guy has different symptoms, for example he often can't complete U-Boot startup at the point it touches Glamo, another outcome is he dies during Glamo driver init in Linux during boot. I never saw these exciting things here, but I do see the other kinds of trouble with Glamo you mentioned during resume and so on. So I believe they are separate issues. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkiRyl4ACgkQOjLpvpq7dMoTkQCcCpfU/StD1H8OtpYecs5tcVaT dAsAnRZE9ZK5hoCNIKOOXm05dberNrJN =7evP -END PGP SIGNATURE- ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: OM2007.2
The SHR bandwagon is well underway, and barreling along. gsm-panel is ported to FSO completely, dialer3 is underway (all of our C interface to FSO is done, barring some tweaks, and the SIM pin UI is done, only a little farther until we're ready to release). We still have a little work to do that you can see on the Stable Hybrid Release wiki page and on the shr-devel projects mailing list. Please do join us now. The activity is mostly happening in svn (of course) and in #openmoko-cdevel on chat.freenode.net. The people most in the know will be primarily Ainulindale and MarcOChapeau, followed by ferric, mw|, mwester, jluis, paulproteus, and wurp (me), in no particular order. Most activity in IRC happens between about 5pm and 1am GMT. Bobby On Thu, Jul 31, 2008 at 1:46 AM, sparky mat [EMAIL PROTECTED] wrote: I still love om2007.2 !! Waiting to jump into the SHR bandwagon as soon as it gets going :-) On Thu, Jul 31, 2008 at 11:38 AM, Jay Vaughan [EMAIL PROTECTED] wrote: I would be curious to know what kind of developer numbers (non-OM employees) would provide support to a fork of OM2007.2 into a purely community driven project? I'll tag along if there is a fork. Does everyone think 2007 is a dead path and that the ASU/FSO course is the only one to follow? Not me! I witnessed all the work that went into OM 2007.2 over the last couple of years - including the days of OE - and when it was all chucked out for 'the new stuff' it was, frankly, a bit miserable. ; -- Jay Vaughan ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support -- If it doesn't make you smile, you're doing something wrong. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: OM2007.2
Jay, Not me! I witnessed all the work that went into OM 2007.2 over the last couple of years - including the days of OE - and when it was all chucked out for 'the new stuff' it was, frankly, a bit miserable. The only thing that was 'chucked out' was the matchbox window manager. It was a great piece of technology and we still like it, but we decided to replace it with raster's Enlightenment and raster did a fantastic job. I think even though the switch was painful at the beginning, we now can be proud of E and have very interesting options going forward. Everything else is still there, including GTK+ if that's what you are looking for. The GTK+ telephony applications are not used by default anymore, but we are working on making them easily installable through the Installer. I hope eventually you will like OM 2008.8 as much as you like OM 2007.2 But forks are welcome, if people out there show us how to do things better, I'm pretty sure I speak for many of us that we will not suffer from NIH syndrome and instead just try to integrate great stuff into our builds. OpenEmbedded makes it very easy for people to do things differently from us, and we invest quite a bit of time and money into it. Best Regards, Wolfgang On Jul 31, 2008, at 2:08 PM, Jay Vaughan wrote: I would be curious to know what kind of developer numbers (non-OM employees) would provide support to a fork of OM2007.2 into a purely community driven project? I'll tag along if there is a fork. Does everyone think 2007 is a dead path and that the ASU/FSO course is the only one to follow? Not me! I witnessed all the work that went into OM 2007.2 over the last couple of years - including the days of OE - and when it was all chucked out for 'the new stuff' it was, frankly, a bit miserable. ; -- Jay Vaughan ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: OM2007.2 continuously freezes!
Marco Trevisan (Treviño) wrote: Hello, since the first time I've used my Freerunner I had serious problems with the GTK 2007.2 version that is simply unusable to me. I've to add to this crying list also the FSO. :( Just tried the milestone 2, it's so nice, but it freezes like the GTK one. Yesterday night I've rebooted the gtk distro, I've upgraded it leaving the phone turned on all the night (making it dim). Next day it was operative and I wasn't quite able to make it freeze (and I've played with it a lot). After some good reboots it freezed again (but it always happens only when I'm playing with it using the touchscreen). So It freezes only when there are inputs... This evening I've tried the FSO getting exactly the same problems so I've figured that problem resides in Xglamo (or maybe in glamo itself? :o) since both the two well-working distros I've tested (Qtopia and ASU) are using different systems (Qtopia writes directly to fb, while ASU uses Xfbdev). Agree? In fact one of the glamo related error I got on the first startup was saying something like spin_lock_irqsave... Maybe I could retry it! Any help to get a log of my freezes (syslogd doesn't help)? -- Treviño's World - Life and Linux http://www.3v1n0.net/ ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: OM2007.2 continuously freezes!
Marco Trevisan (Treviño) wrote: This evening I've tried the FSO getting exactly the same problems so I've figured that problem resides in Xglamo (or maybe in glamo itself? :o) since both the two well-working distros I've tested (Qtopia and ASU) are using different systems (Qtopia writes directly to fb, while ASU uses Xfbdev). Agree? To confirm this, I've just removed from my FSO installation Xglamo and replaced it with Xfbdev and all worked without freezes. It's all a little slower, but it works without freezes. Do you think that this is an hardware problem? :| -- Treviño's World - Life and Linux http://www.3v1n0.net/ ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: OM2007.2
SHR sounds quite interesting.. I really liked the 2007.2 look-n-feel. And, the FSO middleware is supposed to be much superior to gsmd. So, ... yay! :-) On Thu, Jul 31, 2008 at 4:05 AM, Bobby Martin [EMAIL PROTECTED]wrote: The SHR project is right now doing work to maintain 2007.2. Our first work is just to port it to run on the FSO framework since we've found it to be much more stable than gsmd, but we are also very interested in any kind of bugfixes or basic improvements. You can read more (and see how to join the project) at http://wiki.openmoko.org/wiki/Stable_Hybrid_Release Bobby On Wed, Jul 30, 2008 at 5:28 PM, Lon Lentz [EMAIL PROTECTED] wrote: I would be curious to know what kind of developer numbers (non-OM employees) would provide support to a fork of OM2007.2 into a purely community driven project? Does everyone think 2007 is a dead path and that the ASU/FSO course is the only one to follow? On Sun, Jul 27, 2008 at 8:19 AM, Michael 'Mickey' Lauer [EMAIL PROTECTED] wrote: Openmoko does not actively develop OM2007.2, all resources are going into ASU (and the framework initiative). I think we should move to SHR once they have their first release. In the meantime, someone could/should drag all the Openmoko sources into a public Om project repository and continue developing 2007.2 there. If that's going to happen, ping me and I'll change the respective BitBake recipes in OE to pull from the new location. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support -- If it doesn't make you smile, you're doing something wrong. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: OM2007.2 continuously freezes!
Joerg Reisenweber wrote: Am Mo 28. Juli 2008 schrieb Marco Trevisan (Treviño): I should say that my very first Freerunner experience was not so correct since as soon as I've connected it to my wall charger for it's first recharge, it powered on (also if I didn't press the power button before). Since the 1A current rate should be enough both to run it and to charge the battery, I didn't powered it off. Please note the many statements about the need to completely boot up the device to charge battery, to be found spread all over the MLs. Mh what you mean? That I should have had turn my FR immediately off, or that I've not made a bad thing? -- Treviño's World - Life and Linux http://www.3v1n0.net/ ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: OM2007.2 continuously freezes!
Am Mo 28. Juli 2008 schrieb Marco Trevisan (Treviño): Joerg Reisenweber wrote: Am Mo 28. Juli 2008 schrieb Marco Trevisan (Treviño): I should say that my very first Freerunner experience was not so correct since as soon as I've connected it to my wall charger for it's first recharge, it powered on (also if I didn't press the power button before). Since the 1A current rate should be enough both to run it and to charge the battery, I didn't powered it off. Please note the many statements about the need to completely boot up the device to charge battery, to be found spread all over the MLs. Mh what you mean? That I should have had turn my FR immediately off, or that I've not made a bad thing? When you plug in charger, Neo *has* to boot up. Then it will charge. That's been discussed really exhausting now. BTW: please don't send me HTML-mails! Stating you care about format :-D cheers jOERG signature.asc Description: This is a digitally signed message part. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: OM2007.2
Am Samstag 26 Juli 2008 15:17:42 schrieb sparky mat: Hi, newbie here. OM2007.2 is still actively developed right? I mean ASU is an alternate path right? Openmoko does not actively develop OM2007.2, all resources are going into ASU (and the framework initiative). I think we should move to SHR once they have their first release. In the meantime, someone could/should drag all the Openmoko sources into a public Om project repository and continue developing 2007.2 there. If that's going to happen, ping me and I'll change the respective BitBake recipes in OE to pull from the new location. Cheers, -- :M: ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
