Re: wiki spam - urgent
Am 05.12.2011 03:23, schrieb Wolfgang Spraul: We also need more people to be granted erase permissions, i think it is clear from the logs who contributes and is eligible. I apologize, it's not clear to me but I will add erase or admin permissions if you give me a list of user names. I do not believe this solves the bigger problem though, even though the spam deletion efforts are truly amazing. Over on the Qi wiki, we have a much more recent MediaWiki 1.18 or so with visual math captcha etc. I think very soon the Openmoko community has to make a decision whether we want to upgrade the MediaWiki version and include the latest spam fighting extensions, or turn the entire wiki into a read-only resource. Thanks a lot for speaking up, and helping keep the Openmoko wiki clean... Cheers, Wolfgang ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community I think You should try captchas (http://en.wikipedia.org/wiki/CAPTCHA) to verify, which entry is made by an spambot and which not. -- Kind regaards Sebastian Reinhardt ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v37 for GTA04
[cut] Are any of GTA02 owners interested in changes since v35, so that i should do this release also for GTA02? Definitely yes! -- Patryk LeadMan Benderz Linux Registered User #377521 () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v37 for GTA04
Dnia 2011-12-05, pon o godzinie 09:54 +0100, Patryk Benderz pisze: [cut] Are any of GTA02 owners interested in changes since v35, so that i should do this release also for GTA02? Definitely yes! Arghhh! damn Ctrl+Enter! Sent before finished. Just wanted to add: I do not intend to change my board any near future, because of it's relatively high cost, so I would really appreciate your continues work on QtMoko for GTA02. Thanks for your great work! -- Patryk LeadMan Benderz Linux Registered User #377521 () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: wiki spam - urgent
[cut] I do not believe this solves the bigger problem though, even though the spam deletion efforts are truly amazing. Over on the Qi wiki, we have a much more recent MediaWiki 1.18 or so with visual math captcha etc. I think very soon the Openmoko community has to make a decision whether we want to upgrade the MediaWiki version and include the latest spam fighting extensions, Although captchas can be easily handled by bots, I totally agree the wiki engine should be updated. I have even created a ticket regarding this, like years ago, but do not remember getting any response. -- Patryk LeadMan Benderz Linux Registered User #377521 () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Anyone has done a Comparison GTA02 GPS Antenna vs. Nokia N95?
We have seen that the N95 has a quite simple flexible PCB GPS antenna instead of the ceramic patch of the GTA0*. Does anyone of you own both, a N95 and GTA0*? The key issue is not overall sensitivity or TTFF but direction independence. I.e. does it matter much or less to rotate the device by 90 degrees. Any experiences in our community? Nikolaus ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
comment by 'blen2r' about Carrying Case
Hello, There is a comment in the Wiki page http://wiki.openmoko.org/wiki/Carrying_Case made by the user 'blen2r' about contact her/him for more information; but the user page does not exists :-( 'blen2r', please be so kind and contact me off-list; thanks in advance matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e g...@unixarea.de - w http://www.unixarea.de/ UNIX since V7 on PDP-11, UNIX on mainframe since ESER 1055 (IBM /370) UNIX on x86 since SVR4.2 UnixWare 2.1.2, FreeBSD since 2.2.5 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v37 for GTA04
On 12/03/2011 12:00 PM, community-requ...@lists.openmoko.org wrote: thanks (as ususal) for your great work. Yes, please do a GTA02 release if possible. Especially the keyboard was one reason why Qtmoko may have not been as popular as it deserves to be. With the big landscape keyboard this will all change! BR Robin +1 +1 -- ## giacomo 'giotti' mariani gpg --keyserver pool.sks-keyservers.net --recv-key 0x99bfa859 O ASCII ribbon campaign: stop HTML mail www.asciiribbon.org ## ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v37 for GTA04
On 2011-12-05 19:59, Patryk Benderz wrote: Dnia 2011-12-05, pon o godzinie 09:54 +0100, Patryk Benderz pisze: [cut] Are any of GTA02 owners interested in changes since v35, so that i should do this release also for GTA02? Definitely yes! Arghhh! damn Ctrl+Enter! Sent before finished. Just wanted to add: I do not intend to change my board any near future, because of it's relatively high cost, so I would really appreciate your continues work on QtMoko for GTA02. Thanks for your great work! +1 -- Philip Rhoades GPO Box 3411 Sydney NSW 2001 Australia E-mail: p...@pricom.com.au ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v37 for GTA04
Me too Radek - Thanks for the great work - and support via irc. I am currently running V19 in Nand (tweaked some but incredibly stable) , V35 in SD. Please continue to release GTA02 versions :) On Mon, Dec 5, 2011 at 10:55 PM, Philip Rhoades p...@pricom.com.au wrote: On 2011-12-05 19:59, Patryk Benderz wrote: Dnia 2011-12-05, pon o godzinie 09:54 +0100, Patryk Benderz pisze: [cut] Are any of GTA02 owners interested in changes since v35, so that i should do this release also for GTA02? Definitely yes! Arghhh! damn Ctrl+Enter! Sent before finished. Just wanted to add: I do not intend to change my board any near future, because of it's relatively high cost, so I would really appreciate your continues work on QtMoko for GTA02. Thanks for your great work! +1 -- Philip Rhoades GPO Box 3411 Sydney NSW 2001 Australia E-mail: p...@pricom.com.au __**_ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/**mailman/listinfo/communityhttp://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Anyone has done a Comparison GTA02 GPS Antenna vs. Nokia N95?
Le 05/12/2011 10:14, Dr. H. Nikolaus Schaller a écrit : We have seen that the N95 has a quite simple flexible PCB GPS antenna instead of the ceramic patch of the GTA0*. Does anyone of you own both, a N95 and GTA0*? Not sur if relevant, but I have a N9 and a GTA02v5 The key issue is not overall sensitivity or TTFF but direction independence. I.e. does it matter much or less to rotate the device by 90 degrees. Any experiences in our community? Nikolaus ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Anyone has done a Comparison GTA02 GPS Antenna vs. Nokia N95?
On Mon, Dec 5, 2011 at 2:44 PM, Dr. H. Nikolaus Schaller h...@goldelico.comwrote: We have seen that the N95 has a quite simple flexible PCB GPS antenna instead of the ceramic patch of the GTA0*. Does anyone of you own both, a N95 and GTA0*? I have a N95 and a few GTA02s. Let me know what exactly do you want me to test re GPS? Rakshat ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Anyone has done a Comparison GTA02 GPS Antenna vs. Nokia N95?
Hi, Am 05.12.2011 um 15:51 schrieb rakshat hooja: On Mon, Dec 5, 2011 at 2:44 PM, Dr. H. Nikolaus Schaller h...@goldelico.com wrote: We have seen that the N95 has a quite simple flexible PCB GPS antenna instead of the ceramic patch of the GTA0*. Does anyone of you own both, a N95 and GTA0*? I have a N95 and a few GTA02s. Let me know what exactly do you want me to test re GPS? Great! Do you have some software for both that shows the satellite positions and (relative) signal strength? What will be interesting is if the GTA02 sees the satellites more uniform. The background is that the ceramic patch antenna in the GTA02/04 should have a more omnidirectional sensitivity while the N95 has just one flexible PCB with a long wire. And the latter should show some clear direction sensitivity. I.e. if the device is rotated some satellites should become weaker and others stronger. So far the theory we want to probe :) If the N95 antenna does not show such effects, we may have a cheaper approach for future GTA04 variants. And they may be more easily integrated into new cases than the 15x15mm ceramic block... Many thanks for any results, Nikolaus___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: SHR future and way for better stability
Hi Martin, thanks for the updates, I just reflashed my FreeRunner yesterday with latest packages from Testing (I want a reliable phone, but at the same time one in wich I can play around with learning porpouses and SHR gives me that instead of Android) . I want to test latest changes on a partition on SD and have shr-core on NAND, I have a question related to this and Qi and I'll post about it if I can't figure it out on my own. I post this to say thanks to you guys for giving us such an amazing distro that suites just fine for plenty of us, I have a question too, Android ready phones (let's say LG Optimus One) has the capability of running SHR?? as I'm planning to buy one / * *Don't Worry...Be Linux* * Cristian Gómez Alvarez * Ingeniero en Sistemas y Computación --- Universidad de Caldas * Almera Information Management * Comunidad de Software Libre Manizales * Linux User #463617 * Mi Blog: http://cristianpark.sehablalinux.com */ 2011/12/2 Martin Jansa martin.ja...@gmail.com Hi, in last few days we were talking a lot about state of shr-testing, shr-unstable, shr-core and how to improve stability and usability for our users while not slowing down development in our latest version which is shr-core. For details and reasons you can read log from #openmoko-cdevel (13:30) http://logs.nslu2-linux.org/livelogs/openmoko-cdevel/openmoko-cdevel.20111201.txt In the end everybody agreed that we don't have manpower to maintain 3 flavors of SHR which are: shr-testing: There were only 2 maintainers of shr-testing. Sebastian Spaeth for shr-testing2009 and Thomas Zimmermann for shr-testing2010 and 2011.1. There was discussion about more fixes for shr-testing, but nobody sent patches for http://git.openembedded.org/openembedded/log/?h=shr/testing2011.1 so that they could be applied in standard shr-testing feeds. From my perspective shr-testing lacking so far behind shr-unstable and with known issues is not better then tested images and feeds from shr-unstable. shr-unstable: This was based on master branch of openembedded (today called OE-classic) so there was a lot of changes every day which sometimes caused unstable telephony or unusable UI. It was caused mostly because of very limited testing between building it on SHR buildhost and users getting it from shr-unstable feeds by opkg upgrade. But since July 2011 the development in OE-classic was slowing down becase everybody was moving to new layered structure of oe-core/meta-* (google yocto project for more info and fancy video). shr-core: Originaly started in March 2011 as my experimental pet project to evaluate new layers like oe-core/meta-oe, but later all remaining SHR and FSO developers switched from shr-unstable to shr-core too and now we have very lively meta-smartphone repository with BSP layers for our beloved phones and layers for FSO, Aurora and for SHR as distribution. Some stuff from old shr-unstable is still missing and sometimes it's changing too fast for average end user who depends on working telephony. So today we've decided to try something else. Instead of trying to maintain 3 different flavors of shr, we will try harder to provide best experience with shr-core and hopefully migrate all remaining users of shr-testing or shr-unstable to it soon (and then we can rename it to shr-stable :)). Starting with next build we won't push the build output directly to normal feeds, but only to staging feeds for testers which decide to try newer versions. It works like this: 1) http://build.shr-project.org/shr-core nothing will be changed in this feed before it's tested by multiple users from staging feed. 2) http://build.shr-project.org/shr-core-staging/ will contain one directory for each major feature we want to test (like EFL or FSO upgrades) or sometimes just rotated weekly when there isn't something major or dangerous. Each directory has by 3 digit name which identifies the feed (lets call it NNN). Each NNN directory has info.NNN file (and info - info.NNN symlink) where you can read on which revisions was this feed started, which commits were used during populating this feed and when this feed gets closed (or lets say marked as ready for testers). You can also read how all our branches looked when it was closed. Currently there is 001, 002 and latest. 002 is still getting more stuff from live build, so it wasn't closed yet. When we decide that there is enough stuff for testing and the feature is complete, we'll close 002 and redirect build output to new 003. Latest link points to latest but _closed_ feed (so usually highest -1) which is currently 001. If you want to help testing, then best way is to prepare 2nd partition (not the one you're using for daily phone you depend on) and redirect default shr-core feeds to latest closed: sed -i 's#shr-core#shr-core-staging/latest#g'
Re: Anyone has done a Comparison GTA02 GPS Antenna vs. Nokia N95?
On Monday 05 December 2011, Dr. H. Nikolaus Schaller wrote: Hi, Am 05.12.2011 um 15:51 schrieb rakshat hooja: On Mon, Dec 5, 2011 at 2:44 PM, Dr. H. Nikolaus Schaller h...@goldelico.com wrote: We have seen that the N95 has a quite simple flexible PCB GPS antenna instead of the ceramic patch of the GTA0*. Does anyone of you own both, a N95 and GTA0*? I have a N95 and a few GTA02s. Let me know what exactly do you want me to test re GPS? Great! Do you have some software for both that shows the satellite positions and (relative) signal strength? What will be interesting is if the GTA02 sees the satellites more uniform. The background is that the ceramic patch antenna in the GTA02/04 should have a more omnidirectional sensitivity while the N95 has just one flexible PCB with a long wire. ?! Would that actually provide enough signal to get a lock without assistance? I ask partly because it may explain why a friend couldn't get a gps lock on an N95 when on deck on a yacht out of range of mobile networks. GTA02 was reliably coldstarting in ~40s as you'd expect with a clear sky view like that. You need significantly better signal to get the initial fix than to maintain it, as we found with the SD drive strength issue. And the latter should show some clear direction sensitivity. I.e. if the device is rotated some satellites should become weaker and others stronger. So far the theory we want to probe :) If the N95 antenna does not show such effects, we may have a cheaper approach for future GTA04 variants. And they may be more easily integrated into new cases than the 15x15mm ceramic block... Have you looked at an antenna like this? Smaller, cheaper and lower performance than a patch antenna, but probably significantly better than a wire. https://www.sparkfun.com/products/9131 Many thanks for any results, Nikolaus ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: SHR future and way for better stability
Hello Cristian, On Mon, 05 Dec 2011, Cristian Gómez wrote: Hi Martin, thanks for the updates, I just reflashed my FreeRunner yesterday with latest packages from Testing (I want a reliable phone, but at the same time one in wich I can play around with learning porpouses and SHR gives me that instead of Android) . I want to test latest changes on a partition on SD and have shr-core on NAND, I have a question related to this and Qi and I'll post about it if I can't figure it out on my own. I post this to say thanks to you guys for giving us such an amazing distro that suites just fine for plenty of us, I have a question too, Android ready phones (let's say LG Optimus One) has the capability of running SHR?? as I'm planning to buy one unfortunately no. We have no Android based phone working 100% yet. You could check http://wiki.shr-project.org/trac/wiki/Android%20Porting%20Guide to get an idea of what is needed to be done. / * *Don't Worry...Be Linux* * Cristian Gómez Alvarez * Ingeniero en Sistemas y Computación --- Universidad de Caldas * Almera Information Management * Comunidad de Software Libre Manizales * Linux User #463617 * Mi Blog: http://cristianpark.sehablalinux.com */ 2011/12/2 Martin Jansa martin.ja...@gmail.com Hi, in last few days we were talking a lot about state of shr-testing, shr-unstable, shr-core and how to improve stability and usability for our users while not slowing down development in our latest version which is shr-core. For details and reasons you can read log from #openmoko-cdevel (13:30) http://logs.nslu2-linux.org/livelogs/openmoko-cdevel/openmoko-cdevel.20111201.txt In the end everybody agreed that we don't have manpower to maintain 3 flavors of SHR which are: shr-testing: There were only 2 maintainers of shr-testing. Sebastian Spaeth for shr-testing2009 and Thomas Zimmermann for shr-testing2010 and 2011.1. There was discussion about more fixes for shr-testing, but nobody sent patches for http://git.openembedded.org/openembedded/log/?h=shr/testing2011.1 so that they could be applied in standard shr-testing feeds. From my perspective shr-testing lacking so far behind shr-unstable and with known issues is not better then tested images and feeds from shr-unstable. shr-unstable: This was based on master branch of openembedded (today called OE-classic) so there was a lot of changes every day which sometimes caused unstable telephony or unusable UI. It was caused mostly because of very limited testing between building it on SHR buildhost and users getting it from shr-unstable feeds by opkg upgrade. But since July 2011 the development in OE-classic was slowing down becase everybody was moving to new layered structure of oe-core/meta-* (google yocto project for more info and fancy video). shr-core: Originaly started in March 2011 as my experimental pet project to evaluate new layers like oe-core/meta-oe, but later all remaining SHR and FSO developers switched from shr-unstable to shr-core too and now we have very lively meta-smartphone repository with BSP layers for our beloved phones and layers for FSO, Aurora and for SHR as distribution. Some stuff from old shr-unstable is still missing and sometimes it's changing too fast for average end user who depends on working telephony. So today we've decided to try something else. Instead of trying to maintain 3 different flavors of shr, we will try harder to provide best experience with shr-core and hopefully migrate all remaining users of shr-testing or shr-unstable to it soon (and then we can rename it to shr-stable :)). Starting with next build we won't push the build output directly to normal feeds, but only to staging feeds for testers which decide to try newer versions. It works like this: 1) http://build.shr-project.org/shr-core nothing will be changed in this feed before it's tested by multiple users from staging feed. 2) http://build.shr-project.org/shr-core-staging/ will contain one directory for each major feature we want to test (like EFL or FSO upgrades) or sometimes just rotated weekly when there isn't something major or dangerous. Each directory has by 3 digit name which identifies the feed (lets call it NNN). Each NNN directory has info.NNN file (and info - info.NNN symlink) where you can read on which revisions was this feed started, which commits were used during populating this feed and when this feed gets closed (or lets say marked as ready for testers). You can also read how all our branches looked when it was closed. Currently there is 001, 002 and latest. 002 is still getting more stuff from live build, so it wasn't closed yet. When we decide that there is enough stuff for testing and the feature is complete, we'll close 002 and redirect
Quake Catcher Network
Has anyone done any work on using the Freerunner accelerometer for this? http://qcn.stanford.edu/ Liz ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Quake Catcher Network
Liz ed...@billiau.net writes: Has anyone done any work on using the Freerunner accelerometer for this? No but with the GPS yes :-) ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
