Re: Announce: omnewrotate 0.5.0
Hi, Have been playing around with your code and figured out what the possible problem is with the zero values. You essentially try to read 4 packets from the device in 1 read and then decode them into x,y and z assuming they are always send in the same order. However it looks like the sensor/driver does not send a string when the measured value is 0, (can even been seen with hexdump, I'm using SHR with updated kernel from bug 2145 to get around the threshold problem.) If that happens your xyz may get the wrong values resulting in , you'll have to check each message for type and code before you use the value. Efficiency is good, but be careful with shortcuts -- View this message in context: http://n2.nabble.com/Announce%3A-omnewrotate-0.5.0-tp1521019p1598202.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
VAT decrease == cheaper freerunners
Hi all, Just a quick plug to say we've updated our shop with the new VAT rate in the UK; total price including 15% VAT and courier delivery to UK is now £330.05 . Shop is here: https://www.truebox.co.uk/trueboxportal/index.php?wk=shopthiscat=8 We've also got some batteries in for £16 + vat. Antony. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Compatible earphones ...
Just broke my freerunners original headset. Is there a list of compatible models? - not much thats useful on the wiki that Ive been able to find Just that some Nokia smartphone models will work ... Looking more for a headset rather than the original earbuds. BillK -- William Kenworthy [EMAIL PROTECTED] Home in Perth! ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Optimization team update (11/23 ~ 11/29)
I've discovered the same: https://docs.openmoko.org/trac/ticket/2148 Joseph 2008/12/1 William Kenworthy [EMAIL PROTECTED]: Loaded it up and it rebooted fine, but isnt usable. Ive lost the spanner so I cant configure it It goes to sleep automaticly after a few seconds and without the spanner I cant figure out how to disable it (I see you mention that sleep time needs to be reset - but how?). Same if I have it plugged into usb, goes to sleep while I am logged into it. The old settings icon is still present, but does nothing except spin for a few seconds and exits - tried logging in to faultfind it but - you guessed it, phone went to sleep. Its gone back to the huge icons - a real pain, again I cant see how to select the smaller ones without the spanner. Ive lost the terminal keyboard and only have the crappy ones left - unusable for anything serious, like trying to use a terminal to fix things :( I'll try an unmodified 2008.9 in a couple of days and see if my changes to make 2008.9 usable are the cause of the above. The good - gsm registered immediately, but then it went to sleep :( BillK On Sun, 2008-11-30 at 19:50 +0800, John Lee wrote: Dear Community, As Sushama (our new testing team member) indicated in http://lists.openmoko.org/pipermail/devel/2008-November/003493.html , we won't have a release in Nov. Currently the testing team is going to do a full test on the latest testing image. It has all the goodies we did and a lot of improvements over Om2008.9, so please try it and report any error you find. Upgrade howto: From Om2008.9 it's recommanded to upgrade with the following steps: sed -i -e 's%Om2008.8%testing%' /etc/opkg/*.conf /etc/init.d/xserver-nodm stop screen -DR opkg update opkg -force-overwrite upgrade # (please ans Y to all questions) # (the sshd (dropbear) will restart, so you need to reconnect and do # 'screen -DR' again) opkg upgrade shutdown -r now To get the fastest boot time you also need to remove the following packages: opkg remove task-base-nfs task-base-smbfs task-base-bluetooth \ task-base-usbgadget avahi-daemon avahi-autoipd blueprobe \ usb-gadget-mode portmap exquisite exquisite-theme-freerunner \ exquisite-themes Known issues: * GTK redraw problem * some obsolete kernel modules still left in system * must remove 'ro' in kernel boot parameter if you use sd boot. * will purge your incompatible e config, so you might need to set stuffs like suspend time again. Echo: Since there are different hw versions out there (a5, a6, a7), it's impossible to provide one alsa state file that suits all models. However, it seems you can always find appropriate values for your neo. My way is to adjust control.4 Speaker Playback Volume in /usr/share/openmoko/scenarios/gsmhandset.state the max value is 127, 95 works best on my a5. With volume level 3 or 4 in qtopia dialer, the other side can hear no echo while I get good audio quality. Team update: Tick helped to put his touchscreen improvement into stable-tracking, he will work on opkg internals next. Olv moved to look into kernel and fso. Erin will try bluetooth. Julian is working on the GTK redraw issue, please help him out. Jeremy will fix some qtopia bugs and keep working on suspend/resume issues. Regards, John ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community -- William Kenworthy [EMAIL PROTECTED] Home in Perth! ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Freerunner on cover of Linux for you magazine
The Freerunner is the main photo on the December issue of Linux for You Magazine http://www.lfymag.com/currentissue.asp?id=13 Have not read the issue yet but would expect that the lead story should be about the Freerunner too. Regards, Rakshat -- -- Please use Firefox as your web browser. Its protects you from spyware and is also a very feature rich browser. www.firefox.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Optimization team update (11/23 ~ 11/29)
Thanks, also I was bit too rushed. I shut down X which allowed me to stay logged in and find out that the customisations to get the spanner and keyboards had been undone - fixed them and I can now use the phone. The suspend time is fixable from the spanner so the settings isnt needed. Some of my existing apps wont start (pypennotes, ...) so they probably need upgrading. openmoocow (old version) started once out of three tries - left me at a grey screen otherwise. At one point the display died and restarted itself when I tapped a blank part of the home screen. Fonts and widgets are far too large on apps like pythm, tangogps and the like. Tried a test call - no audio :( Probably need to set a profile, but need the settings app for that. BillK On Mon, 2008-12-01 at 12:51 +, Joseph Reeves wrote: I've discovered the same: https://docs.openmoko.org/trac/ticket/2148 Joseph 2008/12/1 William Kenworthy [EMAIL PROTECTED]: Loaded it up and it rebooted fine, but isnt usable. Ive lost the spanner so I cant configure it It goes to sleep automaticly after a few seconds and without the spanner I cant figure out how to disable it (I see you mention that sleep time needs to be reset - but how?). Same if I have it plugged into usb, goes to sleep while I am logged into it. The old settings icon is still present, but does nothing except spin for a few seconds and exits - tried logging in to faultfind it but - you guessed it, phone went to sleep. Its gone back to the huge icons - a real pain, again I cant see how to select the smaller ones without the spanner. Ive lost the terminal keyboard and only have the crappy ones left - unusable for anything serious, like trying to use a terminal to fix things :( I'll try an unmodified 2008.9 in a couple of days and see if my changes to make 2008.9 usable are the cause of the above. The good - gsm registered immediately, but then it went to sleep :( BillK On Sun, 2008-11-30 at 19:50 +0800, John Lee wrote: Dear Community, As Sushama (our new testing team member) indicated in http://lists.openmoko.org/pipermail/devel/2008-November/003493.html , we won't have a release in Nov. Currently the testing team is going to do a full test on the latest testing image. It has all the goodies we did and a lot of improvements over Om2008.9, so please try it and report any error you find. Upgrade howto: From Om2008.9 it's recommanded to upgrade with the following steps: sed -i -e 's%Om2008.8%testing%' /etc/opkg/*.conf /etc/init.d/xserver-nodm stop screen -DR opkg update opkg -force-overwrite upgrade # (please ans Y to all questions) # (the sshd (dropbear) will restart, so you need to reconnect and do # 'screen -DR' again) opkg upgrade shutdown -r now To get the fastest boot time you also need to remove the following packages: opkg remove task-base-nfs task-base-smbfs task-base-bluetooth \ task-base-usbgadget avahi-daemon avahi-autoipd blueprobe \ usb-gadget-mode portmap exquisite exquisite-theme-freerunner \ exquisite-themes Known issues: * GTK redraw problem * some obsolete kernel modules still left in system * must remove 'ro' in kernel boot parameter if you use sd boot. * will purge your incompatible e config, so you might need to set stuffs like suspend time again. Echo: Since there are different hw versions out there (a5, a6, a7), it's impossible to provide one alsa state file that suits all models. However, it seems you can always find appropriate values for your neo. My way is to adjust control.4 Speaker Playback Volume in /usr/share/openmoko/scenarios/gsmhandset.state the max value is 127, 95 works best on my a5. With volume level 3 or 4 in qtopia dialer, the other side can hear no echo while I get good audio quality. Team update: Tick helped to put his touchscreen improvement into stable-tracking, he will work on opkg internals next. Olv moved to look into kernel and fso. Erin will try bluetooth. Julian is working on the GTK redraw issue, please help him out. Jeremy will fix some qtopia bugs and keep working on suspend/resume issues. Regards, John ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community -- William Kenworthy [EMAIL PROTECTED] Home in Perth! ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community -- William Kenworthy [EMAIL PROTECTED] Home in Perth! ___ Openmoko community mailing list
[QTEXTENDED] Very loud noise on (some) incoming calls
I've been using QTE 4.4.2 on my Freerunner for quite some time, now (almost since it's been released). It works fine, especially because I don't use it much as a phone (but still a little). For instance, I have very little to no buzzing problems. For a couple of weeks, I noticed some very strange things : sometimes (it looks like it's more likely to happen when the phone haven't been rebooted for some several days, but then it's only a guess) I got a very high pitched and loud noise when answering incoming calls. Usually, I reboot the phone after that (it's so loud and disturbing I usually remove the battery quickly, for my neighbourhood wouldn't like it much) and it works fine again. Any insight on what might cause that, and/or what I can do to further test it? Thanks. -- Olivier M. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Optimization team update (11/23 ~ 11/29)
Loaded it up and it rebooted fine, but isnt usable. Ive lost the spanner so I cant configure it It goes to sleep automaticly after a few seconds and without the spanner I cant figure out how to disable it (I see you mention that sleep time needs to be reset - but how?). Same if I have it plugged into usb, goes to sleep while I am logged into it. The old settings icon is still present, but does nothing except spin for a few seconds and exits - tried logging in to faultfind it but - you guessed it, phone went to sleep. Its gone back to the huge icons - a real pain, again I cant see how to select the smaller ones without the spanner. Ive lost the terminal keyboard and only have the crappy ones left - unusable for anything serious, like trying to use a terminal to fix things :( I'll try an unmodified 2008.9 in a couple of days and see if my changes to make 2008.9 usable are the cause of the above. The good - gsm registered immediately, but then it went to sleep :( BillK On Sun, 2008-11-30 at 19:50 +0800, John Lee wrote: Dear Community, As Sushama (our new testing team member) indicated in http://lists.openmoko.org/pipermail/devel/2008-November/003493.html , we won't have a release in Nov. Currently the testing team is going to do a full test on the latest testing image. It has all the goodies we did and a lot of improvements over Om2008.9, so please try it and report any error you find. Upgrade howto: From Om2008.9 it's recommanded to upgrade with the following steps: sed -i -e 's%Om2008.8%testing%' /etc/opkg/*.conf /etc/init.d/xserver-nodm stop screen -DR opkg update opkg -force-overwrite upgrade # (please ans Y to all questions) # (the sshd (dropbear) will restart, so you need to reconnect and do # 'screen -DR' again) opkg upgrade shutdown -r now To get the fastest boot time you also need to remove the following packages: opkg remove task-base-nfs task-base-smbfs task-base-bluetooth \ task-base-usbgadget avahi-daemon avahi-autoipd blueprobe \ usb-gadget-mode portmap exquisite exquisite-theme-freerunner \ exquisite-themes Known issues: * GTK redraw problem * some obsolete kernel modules still left in system * must remove 'ro' in kernel boot parameter if you use sd boot. * will purge your incompatible e config, so you might need to set stuffs like suspend time again. Echo: Since there are different hw versions out there (a5, a6, a7), it's impossible to provide one alsa state file that suits all models. However, it seems you can always find appropriate values for your neo. My way is to adjust control.4 Speaker Playback Volume in /usr/share/openmoko/scenarios/gsmhandset.state the max value is 127, 95 works best on my a5. With volume level 3 or 4 in qtopia dialer, the other side can hear no echo while I get good audio quality. Team update: Tick helped to put his touchscreen improvement into stable-tracking, he will work on opkg internals next. Olv moved to look into kernel and fso. Erin will try bluetooth. Julian is working on the GTK redraw issue, please help him out. Jeremy will fix some qtopia bugs and keep working on suspend/resume issues. Regards, John ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community -- William Kenworthy [EMAIL PROTECTED] Home in Perth! ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Optimization team update (11/23 ~ 11/29)
On Mon, 01 Dec 2008 22:22:28 +0900 William Kenworthy [EMAIL PROTECTED] wrote: openmoocow (old version) started once out of three tries - left me at a grey screen otherwise. This is really my fault, due to a combination of MooCow's architecture in that version and the accelerometer driver behaviour. Try the newer version - it should work much better. Tom ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Optimization team update (11/23 ~ 11/29)
On Mon, Dec 01, 2008 at 10:22:28PM +0900, William Kenworthy wrote: Thanks, also I was bit too rushed. I shut down X which allowed me to stay logged in and find out that the customisations to get the spanner and keyboards had been undone - fixed them and I can now use the phone. The suspend time is fixable from the spanner so the settings isnt needed. Some of my existing apps wont start (pypennotes, ...) so they probably need upgrading. openmoocow (old version) started once out of three tries - left me at a grey screen otherwise. At one point the display died and restarted itself when I tapped a blank part of the home screen. Fonts and widgets are far too large on apps like pythm, tangogps and the like. Tried a test call - no audio :( thanks for the feedback! that sounds like #2140. have you tried to tune up the volume ? Probably need to set a profile, but need the settings app for that. BillK On Mon, 2008-12-01 at 12:51 +, Joseph Reeves wrote: I've discovered the same: https://docs.openmoko.org/trac/ticket/2148 Joseph 2008/12/1 William Kenworthy [EMAIL PROTECTED]: Loaded it up and it rebooted fine, but isnt usable. Ive lost the spanner so I cant configure it It goes to sleep automaticly after a few seconds and without the spanner I cant figure out how to disable it (I see you mention that sleep time needs to be reset - but how?). Same if I have it plugged into usb, goes to sleep while I am logged into it. The old settings icon is still present, but does nothing except spin for a few seconds and exits - tried logging in to faultfind it but - you guessed it, phone went to sleep. Its gone back to the huge icons - a real pain, again I cant see how to select the smaller ones without the spanner. Ive lost the terminal keyboard and only have the crappy ones left - unusable for anything serious, like trying to use a terminal to fix things :( I'll try an unmodified 2008.9 in a couple of days and see if my changes to make 2008.9 usable are the cause of the above. The good - gsm registered immediately, but then it went to sleep :( BillK On Sun, 2008-11-30 at 19:50 +0800, John Lee wrote: Dear Community, As Sushama (our new testing team member) indicated in http://lists.openmoko.org/pipermail/devel/2008-November/003493.html , we won't have a release in Nov. Currently the testing team is going to do a full test on the latest testing image. It has all the goodies we did and a lot of improvements over Om2008.9, so please try it and report any error you find. Upgrade howto: From Om2008.9 it's recommanded to upgrade with the following steps: sed -i -e 's%Om2008.8%testing%' /etc/opkg/*.conf /etc/init.d/xserver-nodm stop screen -DR opkg update opkg -force-overwrite upgrade # (please ans Y to all questions) # (the sshd (dropbear) will restart, so you need to reconnect and do # 'screen -DR' again) opkg upgrade shutdown -r now To get the fastest boot time you also need to remove the following packages: opkg remove task-base-nfs task-base-smbfs task-base-bluetooth \ task-base-usbgadget avahi-daemon avahi-autoipd blueprobe \ usb-gadget-mode portmap exquisite exquisite-theme-freerunner \ exquisite-themes Known issues: * GTK redraw problem * some obsolete kernel modules still left in system * must remove 'ro' in kernel boot parameter if you use sd boot. * will purge your incompatible e config, so you might need to set stuffs like suspend time again. Echo: Since there are different hw versions out there (a5, a6, a7), it's impossible to provide one alsa state file that suits all models. However, it seems you can always find appropriate values for your neo. My way is to adjust control.4 Speaker Playback Volume in /usr/share/openmoko/scenarios/gsmhandset.state the max value is 127, 95 works best on my a5. With volume level 3 or 4 in qtopia dialer, the other side can hear no echo while I get good audio quality. Team update: Tick helped to put his touchscreen improvement into stable-tracking, he will work on opkg internals next. Olv moved to look into kernel and fso. Erin will try bluetooth. Julian is working on the GTK redraw issue, please help him out. Jeremy will fix some qtopia bugs and keep working on suspend/resume issues. Regards, John ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community -- William Kenworthy [EMAIL PROTECTED] Home in Perth! ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Optimization team update (11/23 ~ 11/29)
On Mon, Dec 01, 2008 at 10:22:28PM +0900, William Kenworthy wrote: Thanks, also I was bit too rushed. I shut down X which allowed me to stay logged in and find out that the customisations to get the spanner and keyboards had been undone - fixed them and I can now use the phone. The suspend time is fixable from the spanner so the settings isnt needed. Some of my existing apps wont start (pypennotes, ...) so they probably need upgrading. openmoocow (old version) started once out of three tries - left me at a grey screen otherwise. At one point the display died and restarted itself when I tapped a blank part of the home screen. Fonts and widgets are far too large on apps like pythm, tangogps and the like. Just checking: Do you have moko-gtk-engine and moko-gtk-theme installed ? Tried a test call - no audio :( Probably need to set a profile, but need the settings app for that. BillK On Mon, 2008-12-01 at 12:51 +, Joseph Reeves wrote: I've discovered the same: https://docs.openmoko.org/trac/ticket/2148 Joseph 2008/12/1 William Kenworthy [EMAIL PROTECTED]: Loaded it up and it rebooted fine, but isnt usable. Ive lost the spanner so I cant configure it It goes to sleep automaticly after a few seconds and without the spanner I cant figure out how to disable it (I see you mention that sleep time needs to be reset - but how?). Same if I have it plugged into usb, goes to sleep while I am logged into it. The old settings icon is still present, but does nothing except spin for a few seconds and exits - tried logging in to faultfind it but - you guessed it, phone went to sleep. Its gone back to the huge icons - a real pain, again I cant see how to select the smaller ones without the spanner. Ive lost the terminal keyboard and only have the crappy ones left - unusable for anything serious, like trying to use a terminal to fix things :( I'll try an unmodified 2008.9 in a couple of days and see if my changes to make 2008.9 usable are the cause of the above. The good - gsm registered immediately, but then it went to sleep :( BillK On Sun, 2008-11-30 at 19:50 +0800, John Lee wrote: Dear Community, As Sushama (our new testing team member) indicated in http://lists.openmoko.org/pipermail/devel/2008-November/003493.html , we won't have a release in Nov. Currently the testing team is going to do a full test on the latest testing image. It has all the goodies we did and a lot of improvements over Om2008.9, so please try it and report any error you find. Upgrade howto: From Om2008.9 it's recommanded to upgrade with the following steps: sed -i -e 's%Om2008.8%testing%' /etc/opkg/*.conf /etc/init.d/xserver-nodm stop screen -DR opkg update opkg -force-overwrite upgrade # (please ans Y to all questions) # (the sshd (dropbear) will restart, so you need to reconnect and do # 'screen -DR' again) opkg upgrade shutdown -r now To get the fastest boot time you also need to remove the following packages: opkg remove task-base-nfs task-base-smbfs task-base-bluetooth \ task-base-usbgadget avahi-daemon avahi-autoipd blueprobe \ usb-gadget-mode portmap exquisite exquisite-theme-freerunner \ exquisite-themes Known issues: * GTK redraw problem * some obsolete kernel modules still left in system * must remove 'ro' in kernel boot parameter if you use sd boot. * will purge your incompatible e config, so you might need to set stuffs like suspend time again. Echo: Since there are different hw versions out there (a5, a6, a7), it's impossible to provide one alsa state file that suits all models. However, it seems you can always find appropriate values for your neo. My way is to adjust control.4 Speaker Playback Volume in /usr/share/openmoko/scenarios/gsmhandset.state the max value is 127, 95 works best on my a5. With volume level 3 or 4 in qtopia dialer, the other side can hear no echo while I get good audio quality. Team update: Tick helped to put his touchscreen improvement into stable-tracking, he will work on opkg internals next. Olv moved to look into kernel and fso. Erin will try bluetooth. Julian is working on the GTK redraw issue, please help him out. Jeremy will fix some qtopia bugs and keep working on suspend/resume issues. Regards, John ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community -- William Kenworthy [EMAIL PROTECTED] Home in Perth! ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Optimization team update (11/23 ~ 11/29)
I've got: [EMAIL PROTECTED]:~# opkg status moko-gtk-engine Package: moko-gtk-engine Version: 0.1.0+svnr4734-r0 Depends: moko-gtk-theme, gtk+ (= 2.12.11), libatk-1.0-0 (= 1.20.0), pango (= 1.18.3), libcairo2 (= 1.6.4), libgobject-2.0-0 (= 2.16.4), libgmodule-2.0-0 (= 2.16.4), libc6 (= 2.6.1), libglib-2.0-0 (= 2.16.4) Status: install user installed Architecture: armv4t [EMAIL PROTECTED]:~# And TangoGPS looks fine. There seems to be a strange problem with gtk apps that, when first loaded, they appear to freeze, but if you go back to home then select the open app from the top drop down list again, they work fine. It's an odd one to reproduce though, so I won't file a ticket yet. Joseph 2008/12/1 John Lee [EMAIL PROTECTED]: On Mon, Dec 01, 2008 at 10:22:28PM +0900, William Kenworthy wrote: Thanks, also I was bit too rushed. I shut down X which allowed me to stay logged in and find out that the customisations to get the spanner and keyboards had been undone - fixed them and I can now use the phone. The suspend time is fixable from the spanner so the settings isnt needed. Some of my existing apps wont start (pypennotes, ...) so they probably need upgrading. openmoocow (old version) started once out of three tries - left me at a grey screen otherwise. At one point the display died and restarted itself when I tapped a blank part of the home screen. Fonts and widgets are far too large on apps like pythm, tangogps and the like. Just checking: Do you have moko-gtk-engine and moko-gtk-theme installed ? Tried a test call - no audio :( Probably need to set a profile, but need the settings app for that. BillK On Mon, 2008-12-01 at 12:51 +, Joseph Reeves wrote: I've discovered the same: https://docs.openmoko.org/trac/ticket/2148 Joseph 2008/12/1 William Kenworthy [EMAIL PROTECTED]: Loaded it up and it rebooted fine, but isnt usable. Ive lost the spanner so I cant configure it It goes to sleep automaticly after a few seconds and without the spanner I cant figure out how to disable it (I see you mention that sleep time needs to be reset - but how?). Same if I have it plugged into usb, goes to sleep while I am logged into it. The old settings icon is still present, but does nothing except spin for a few seconds and exits - tried logging in to faultfind it but - you guessed it, phone went to sleep. Its gone back to the huge icons - a real pain, again I cant see how to select the smaller ones without the spanner. Ive lost the terminal keyboard and only have the crappy ones left - unusable for anything serious, like trying to use a terminal to fix things :( I'll try an unmodified 2008.9 in a couple of days and see if my changes to make 2008.9 usable are the cause of the above. The good - gsm registered immediately, but then it went to sleep :( BillK On Sun, 2008-11-30 at 19:50 +0800, John Lee wrote: Dear Community, As Sushama (our new testing team member) indicated in http://lists.openmoko.org/pipermail/devel/2008-November/003493.html , we won't have a release in Nov. Currently the testing team is going to do a full test on the latest testing image. It has all the goodies we did and a lot of improvements over Om2008.9, so please try it and report any error you find. Upgrade howto: From Om2008.9 it's recommanded to upgrade with the following steps: sed -i -e 's%Om2008.8%testing%' /etc/opkg/*.conf /etc/init.d/xserver-nodm stop screen -DR opkg update opkg -force-overwrite upgrade # (please ans Y to all questions) # (the sshd (dropbear) will restart, so you need to reconnect and do # 'screen -DR' again) opkg upgrade shutdown -r now To get the fastest boot time you also need to remove the following packages: opkg remove task-base-nfs task-base-smbfs task-base-bluetooth \ task-base-usbgadget avahi-daemon avahi-autoipd blueprobe \ usb-gadget-mode portmap exquisite exquisite-theme-freerunner \ exquisite-themes Known issues: * GTK redraw problem * some obsolete kernel modules still left in system * must remove 'ro' in kernel boot parameter if you use sd boot. * will purge your incompatible e config, so you might need to set stuffs like suspend time again. Echo: Since there are different hw versions out there (a5, a6, a7), it's impossible to provide one alsa state file that suits all models. However, it seems you can always find appropriate values for your neo. My way is to adjust control.4 Speaker Playback Volume in /usr/share/openmoko/scenarios/gsmhandset.state the max value is 127, 95 works best on my a5. With volume level 3 or 4 in qtopia dialer, the other side can hear no echo while I get good audio quality. Team update: Tick helped to put his touchscreen improvement into stable-tracking, he will
Re: Optimization team update (11/23 ~ 11/29)
On Mon, 1 Dec 2008 15:31:03 + Joseph Reeves [EMAIL PROTECTED] wrote: There seems to be a strange problem with gtk apps that, when first loaded, they appear to freeze, but if you go back to home then select the open app from the top drop down list again, they work fine. It's an odd one to reproduce though, so I won't file a ticket yet. That's exactly bug #1946, so no need to file a ticket... https://docs.openmoko.org/trac/ticket/1946 Tom ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [QTEXTENDED] Very loud noise on (some) incoming calls
I'm also using QTE 4.4.2, and I get this behaviour consistently after I configure a gprs internet connection. On Saturday I noticed it for the first time without trying to configure a gprs connection - but I'm not sure what triggered it. I normally try to reboot every couple of days, but hadn't in a while... It was fine after a reboot... I guess you just need to pretend the FR is a windows box and reboot it every couple of days... :-) Warren On Mon, Dec 1, 2008 at 8:24 AM, Olivier Migeot [EMAIL PROTECTED] wrote: I've been using QTE 4.4.2 on my Freerunner for quite some time, now (almost since it's been released). It works fine, especially because I don't use it much as a phone (but still a little). For instance, I have very little to no buzzing problems. For a couple of weeks, I noticed some very strange things : sometimes (it looks like it's more likely to happen when the phone haven't been rebooted for some several days, but then it's only a guess) I got a very high pitched and loud noise when answering incoming calls. Usually, I reboot the phone after that (it's so loud and disturbing I usually remove the battery quickly, for my neighbourhood wouldn't like it much) and it works fine again. Any insight on what might cause that, and/or what I can do to further test it? Thanks. -- Olivier M. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [debian/fso] Re: zhone and sms
On 28.11.2008, at 11:05, arne anka wrote: dunno. but to help, enable logging to file in framework.conf, open a bug at the fso trac and append the log (remove any private information before, like phone numbers and the sms content). Do you mean that I should check zhone.log? Boštjan ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [debian/fso] Re: zhone and sms
Do you mean that I should check zhone.log? no, the log file you configured for frameworkd. see /etc/frameworkd.conf. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [QTEXTENDED] Very loud noise on (some) incoming calls
On Mon, Dec 1, 2008 at 4:51 PM, Warren Baird [EMAIL PROTECTED] wrote: I'm also using QTE 4.4.2, and I get this behaviour consistently after I configure a gprs internet connection. On Saturday I noticed it for the first time without trying to configure a gprs connection - but I'm not sure what triggered it. I normally try to reboot every couple of days, but hadn't in a while... It was fine after a reboot... I guess you just need to pretend the FR is a windows box and reboot it every couple of days... :-) Well, thanks for your answer, at least I'm not alone :) I can state the GPRS connection isn't the (only) reason, for I never configured any on my phone. Rebooting is a quick-fix, but without knowing how often one should do it, it's kinda pointless :/ Regards, -- Olivier M. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Optimization team update (11/23 ~ 11/29)
Hi John, All, Just upgraded from 2008.9. Things to mention: - Boot time decreased. A lot! Thumbs up and a great Thank you for that :) - Also, startup time for applications (dialer) seems to have decreased. - As mentioned elsewhere, Enlightenment configuration was reset to not show the spanner and as the settings utility is unusable and the phone tends to suspend after 31 seconds, it is pretty unusable until one switches Enlightenment themes according to http://wiki.openmoko.org/wiki/Keyboard_Toggle (bottom of the page). - Even after disabling suspend I am having problems. In particular I am now experiencing WSoD even after screen blank (probably bug #2115: https://docs.openmoko.org/trac/ticket/2115 ). I suppose I need to disable screen blank too for now? Nevertheless, even though there are problems it's good to see progress. Keep up the good work. Regards, Andreas John Lee wrote: Dear Community, As Sushama (our new testing team member) indicated in http://lists.openmoko.org/pipermail/devel/2008-November/003493.html , we won't have a release in Nov. Currently the testing team is going to do a full test on the latest testing image. It has all the goodies we did and a lot of improvements over Om2008.9, so please try it and report any error you find. Upgrade howto: From Om2008.9 it's recommanded to upgrade with the following steps: sed -i -e 's%Om2008.8%testing%' /etc/opkg/*.conf /etc/init.d/xserver-nodm stop screen -DR opkg update opkg -force-overwrite upgrade # (please ans Y to all questions) # (the sshd (dropbear) will restart, so you need to reconnect and do # 'screen -DR' again) opkg upgrade shutdown -r now To get the fastest boot time you also need to remove the following packages: opkg remove task-base-nfs task-base-smbfs task-base-bluetooth \ task-base-usbgadget avahi-daemon avahi-autoipd blueprobe \ usb-gadget-mode portmap exquisite exquisite-theme-freerunner \ exquisite-themes Known issues: * GTK redraw problem * some obsolete kernel modules still left in system * must remove 'ro' in kernel boot parameter if you use sd boot. * will purge your incompatible e config, so you might need to set stuffs like suspend time again. Echo: Since there are different hw versions out there (a5, a6, a7), it's impossible to provide one alsa state file that suits all models. However, it seems you can always find appropriate values for your neo. My way is to adjust control.4 Speaker Playback Volume in /usr/share/openmoko/scenarios/gsmhandset.state the max value is 127, 95 works best on my a5. With volume level 3 or 4 in qtopia dialer, the other side can hear no echo while I get good audio quality. Team update: Tick helped to put his touchscreen improvement into stable-tracking, he will work on opkg internals next. Olv moved to look into kernel and fso. Erin will try bluetooth. Julian is working on the GTK redraw issue, please help him out. Jeremy will fix some qtopia bugs and keep working on suspend/resume issues. Regards, John ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Optimization team update (11/23 ~ 11/29)
Thanks Tom, Looks like _the_ big problem I've come across is well known to a fair few people. Cheers, Joseph 2008/12/1 Thomas White [EMAIL PROTECTED]: On Mon, 1 Dec 2008 15:31:03 + Joseph Reeves [EMAIL PROTECTED] wrote: There seems to be a strange problem with gtk apps that, when first loaded, they appear to freeze, but if you go back to home then select the open app from the top drop down list again, they work fine. It's an odd one to reproduce though, so I won't file a ticket yet. That's exactly bug #1946, so no need to file a ticket... https://docs.openmoko.org/trac/ticket/1946 Tom ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [debian/fso] Re: zhone and sms
no, the log file you configured for frameworkd. see /etc/ frameworkd.conf. OK. I've tried to uncomment log_to=syslog and the FR hanged on the connecting w/ dbus. The same happens if I add VERBOSE=yes. Boštjan ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [debian/fso] Re: zhone and sms
OK. I've tried to uncomment log_to=syslog and the FR hanged on the connecting w/ dbus. The same happens if I add VERBOSE=yes. you've got most likely no syslog installed. configure a file somewhere where it survives reboot (and bear in mind that it grows fast). ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Android on Freerunner from Koolu...
Greetings all, I just wanted to give a quick update on the status of Android on the Freerunner as supported by Koolu. Currently we are looking at licensing issues with respect to the global market with particular reference to the media codecs included in Android, but are still making great progress on an image for distribution. Ironically, this puts us in a situation where it will be easier for us to release actual source code, build tools and instructions, before actual binary images. We will be announcing everything tomorrow from a telecommunications conference in Brazil. In the last two years of working with Koolu, I have had the opportunity of being in direct tutelage of Jon Maddog Hall, which has helped shape my views on open source. With his permission, I am posting the message below on his behalf to insure that it made it to the community list. Best regards, Brian Code Greetings to the list, First of all, I might say the the role of Chief Advocate for Openmoko was the idea of the conference organizers, not me. I was happy to be either the CTO of Koolu or the Executive Director of Linux International, but since I was at the conference at the request of Openmoko, and since I was on a panel representing the openness of their philosophy, the organizers wanted a title that reflected that... Secondly, Koolu does work with Openmoko in many ways, so I did not indicate that we were working together. We are working together. Third, I am an open source advocate, actually leaning toward Free Software. But I am also a pragmatist, and there are some times when you have to tread lightly with openness until you find out what is going on. So a short time ago Google released a massive amount of code called Android. Since Koolu was not part of the Open Handset Alliance we could only look at it from the outside like a lot of other people. Recently an issue was brought up regarding patent royalties due on various codecs inside of the code. Even though the code itself is under the Apache license, in various jursidictions royalties have to be paid on the distribution of that code due to patents that are infringed. Sometimes a lot of these royalties are bunded with the hardware, so software people do not really have to recognize them. Some distributions of Linux get around this by writing code that allows for these royalty-bearing segments to be dynamically linked separately from a code build. Ubuntu and Debian both do this as distributions. Unfortunately we found that while the royalty bearing code for Android was in a separate source code directory, the code could not be built without that royalty bearing code being included in the binaries. This created the issue of Openmoko removing the binaries from their server. In my opinion they did the right thing. Rather than jeoprodise Android, Openmoko and Google, they temporarily removed the offending code. I say temporarily because I feel that once the issue is completely understood there will be a work-around that will allow open source developers to move ahead. In the meantime our team of programmers is working on the issue. We are talking with the companies that originally wrote the code trying to understand the exact use of it, and we are talking with the licensing agencies to understand the implications. I am encouraging the company that first introduced the multimedia codecs to work with the Open Handset Alliance to identify these areas and other potentially royalty-bearing areas that might affect Android, and to make them more visible, so people can understand and deal with them. I can not speak entirely for the company of Koolu. While I am the CTO, I am not a major stockholder nor a director of the company. I can tell you that Andrew Greig, the CEO and Brian Code, the Technical Director both know, understand and appreciate Open Source. As far as I know it is the intention of Koolu to contribute back the changes that we make to the Android code to the community. Koolu understands the leverage that is inherent in Open Source. Recently we made some announcements of timeframes for putting the code up on the web. Those were formulated before we knew about this royalty issue, but our intent is to proceed as fast as possible to meet those goals. I hope this answers people's questions and issues around this. Warmest regards, maddog ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Compatible earphones ...
Am Monday 01 December 2008 13:00:15 schrieb [EMAIL PROTECTED]: William Kenworthy [EMAIL PROTECTED] writes: Just broke my freerunners original headset. Is there a list of compatible models? - not much thats useful on the wiki that Ive been able to find Just that some Nokia smartphone models will work ... Looking more for a headset rather than the original earbuds. BillK Try to keep the broken headset around anyway. It can be useful to solder a headphone jack to it so you can use whatever headphones you like with it. The 2.5mm 4-pole plug seems hard to come by. And please add your results to [1] when you've got something working! :) [1] http://wiki.openmoko.org/wiki/Headset -- Marcel ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: VAT decrease == cheaper freerunners
Unfortunately, Germany did not (yet?) reduce VAT... So we have to stay at 349 EUR incl. 19 %. http://www.handheld-linux.com/wiki.php?page=Neo%20Freerunner If they reduce, we will as well... Nikolaus Am 01.12.2008 um 12:02 schrieb Antony King: Hi all, Just a quick plug to say we've updated our shop with the new VAT rate in the UK; total price including 15% VAT and courier delivery to UK is now £330.05 . Shop is here: https://www.truebox.co.uk/trueboxportal/index.php?wk=shopthiscat=8 We've also got some batteries in for £16 + vat. Antony. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[debian] sources
deb http://ftp2.de.debian.org/debian unstable main deb http://ftp2.de.debian.org/debian experimental main deb http://pkg-fso.alioth.debian.org/debian unstable main is it possible to have something less dangerous for everyday life? ;-) thanks d ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: VAT decrease == cheaper freerunners
I should add that we also have some Accessories. So if you are looking for an Xmas present to extend your Freerunner ;) http://www.handheld-linux.com/wiki.php?page=Neo%20Freerunner%3AAccessories Am 01.12.2008 um 19:57 schrieb Dr. H. Nikolaus Schaller: Unfortunately, Germany did not (yet?) reduce VAT... So we have to stay at 349 EUR incl. 19 %. http://www.handheld-linux.com/wiki.php?page=Neo%20Freerunner If they reduce, we will as well... ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
SHR applications on Debian
Hi everyone, I'm not requesting any packages of the SHR applications for debian, I want to make them myself. (The applications, not the packages) I thought I'd just follow the build instructions on SHR's trac, but I'm not sure if that's the way to go. It talks more about building an image on a desktop instead of applications on a freerunner. So, is there another way, or are the build instructions correct? Greetings, Jelle De Loecker ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [debian] sources
Hi, Am Montag, den 01.12.2008, 20:56 +0100 schrieb Davide Scaini: deb http://ftp2.de.debian.org/debian unstable main deb http://ftp2.de.debian.org/debian experimental main deb http://pkg-fso.alioth.debian.org/debian unstable main is it possible to have something less dangerous for everyday life? ;-) thanks You can of course install Debian stable on your FreeRunner, but it won’t contain any OpenMoko-specific software. And I wouldn’t consider unstabe exactly dangerous – I’m using it since over 6 years on my work machine. Greetings, Joachim -- Joachim nomeata Breitner Debian Developer [EMAIL PROTECTED] | ICQ# 74513189 | GPG-Keyid: 4743206C JID: [EMAIL PROTECTED] | http://people.debian.org/~nomeata signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: SHR applications on Debian
Hi, Am Montag, den 01.12.2008, 21:24 +0100 schrieb Jelle De Loecker: I'm not requesting any packages of the SHR applications for debian, I want to make them myself. (The applications, not the packages) I thought I'd just follow the build instructions on SHR's trac, but I'm not sure if that's the way to go. It talks more about building an image on a desktop instead of applications on a freerunner. So, is there another way, or are the build instructions correct? the Debian way of building something is always “on” the machine (so either the FreeRunner, or an armel qemu image which might be faster). There, you can just build the SHR apps using the regular $ ./configure make make install step. I have started to package SHR for Debian, but it misses some enlightenmen libraries that will be packaged by the pkg-e team eventually, but just hasn’t been done yet. Greetings, Joachim -- Joachim nomeata Breitner Debian Developer [EMAIL PROTECTED] | ICQ# 74513189 | GPG-Keyid: 4743206C JID: [EMAIL PROTECTED] | http://people.debian.org/~nomeata signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Community update, Dec. 1st, 2008
Dear friends, Good evening/day/afternoon (whatever your TZ is). This is our sixth community community update. Congratulations to Valério, he won the first 24h-coding prize at Sapo Codebits by turning freerunner in a mouse and gamepad using the accelerometers. Code will be merged with ReMoko. Another month goes by without a 2008.x release, but Openmoko's optimization team invites volunteers to install the latest testing image and report. And we have lots of newer applications. Contents (read the hypertext version at : http://wiki.openmoko.org/wiki/Community_Updates/December_1st%2C_2008 ) * 1 Applications * 2 Distributions * 3 Hardware * 4 Kernel and bootloaders * 5 Community [edit] Applications * A new Pong game. * Newrotate 0.5 is out, uses really little CPU now. * Gtkaddpoi 0.5 : software to add a Point Of Interest to TangoGPS. * neoqplayer 0.1 : codenamed frog. A media player that conserves CPU cycles. * First release of TwitterMoko, a twitter client for openmoko. * ShortOm 0.2 : an application/shell launcher. * openmoko-panel-plugin 0.6 : support for fso frameworkd milestone 4. * Unison works. It is a file-synchronization tool for Unix and Windows. It determines all differences between two directory trees and lets the user decide, how to proceed with every differing file. * OpenMooCow 0.2. Mooes more, runs headless, tickleable. * AaTerm, an improved openmoko-terminal2. * Azmodie proposed a solution for right and middle clicking: Use the gnome accessibility tool mousetweaks (.deb). * Auxlaunch 0.6, a finger-friendly app launcher and window switcher. Bugfixes/integration update. [edit] Distributions * SHR: a newer snapshot is available. * ASU: The official 2008.9 image is back online without the questionable audio codecs. This month's 2008.11 is not going to see the light, but here are instructions to install the current 2008.testing build. It has all the goodies from optimization team (read their progress report, previous reports), i.e. about 1 minute boot and Volume control during call... The bug count is decreasing in the latest testing report. See also the previous testing report hardware revision A7 with capacitor was declared good for mess production ;). * For Android: Walter Chang made a soft keyboard. Rui Castro implemented an OnScreen Keyboard. It was immediately included in Sean's image, to be released at the usual page without mp3 support soon. Koolu posted an update on their release plans: they too are busy dealing with the audio codecs IP issue. * Following a post on the French wiki, the Distribution page was updated by adding FIVE new distros: Hackable:1, NeoPwn, RunningBear, Poky and PyNeo. [edit] Hardware * For an armband to hold the Freerunner while exercising, Gilles Casse recommends the UMC-3 from Case Logic. * Patrick Beck grafted a light on a miniusb - connector, to make an OpenMoko flash light. More lumens the bright white screen one get with the Flashlight script. * The official fix for buzzing is to add a 100uF capacity here and replace one resistor there. Technical details to be published in an Openmoko rework SOP paper. The company is looking at how to fix *all* devices sold. * The Calypso GSM firmware moko10 was released, it fixes ticket 666 for those users with 3G SIM cards. A few Indiana Jones types did try and follow the wiki instructions to reflash, most with success, some with hubris (def: excessive pride). For the rest of us, a user-friendly installer is being prepared. [edit] Kernel and bootloaders Big bad bug of the month prize goes to ticket 1841 white screen of death (WSOD) after resume. This bug shows itself only by cold weather! Nicolas Dufresne found out that the culprit was probably a too tight timing in the JBT driver. Hopefully this will be fixed soon now, and we can all switch to Linux 2.6.28 happily everafter. Developers must read Andy's explanations about kernel branch management. * Preview upcoming changes to the /sys directory. * Improvements to the touchscreen, backlight and accelerometer kernel drivers. * Qi gets lots of GTA03 love, audio back and a memory test ability (called when there are no valid kernels). * The opkg package manager was patched to cache downloaded files. [edit] Community * Removed the tagcloud extension that messed up with page formatting. * There are many links to nice Ringtones on the wiki, but the page and the whole topic need a good overhaul. * GnuPhone here we come: Sten Kvamme explains how to make a call from the command line (on FSO). * For your pleasure, here is the OpenMoko Jokes page. Thanks to the community, keep them coming ;) We (Coolcat and I) are also thinking about adding a pic of the week to the homepage, so stay tuned. * Courtesy of Dale Maggee, here and here are a few funny splash screens. Note that you already trust Dale
Re: SHR applications on Debian
Op maandag 01-12-2008 om 21:33 uur [tijdzone +0100], schreef Joachim Breitner: Hi, Am Montag, den 01.12.2008, 21:24 +0100 schrieb Jelle De Loecker: I'm not requesting any packages of the SHR applications for debian, I want to make them myself. (The applications, not the packages) So, is there another way, or are the build instructions correct? the Debian way of building something is always “on” the machine (so either the FreeRunner, or an armel qemu image which might be faster). There, you can just build the SHR apps using the regular $ ./configure make make install step. I have started to package SHR for Debian, but it misses some enlightenmen libraries that will be packaged by the pkg-e team eventually, but just hasn’t been done yet. Greetings, Joachim Great! When I finally discover why the phone completely freezes when downloading a bunch of files I'll give it a go! ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Windows on openmoko?
Maybe somebody is porting ReactOS to it already? Audrius ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Optimization team update (11/23 ~ 11/29)
2008/11/30 John Lee [EMAIL PROTECTED]: Echo: Since there are different hw versions out there (a5, a6, a7), it's impossible to provide one alsa state file that suits all models. However, it seems you can always find appropriate values for your neo. My way is to adjust control.4 Speaker Playback Volume in /usr/share/openmoko/scenarios/gsmhandset.state the max value is 127, 95 works best on my a5. With volume level 3 or 4 in qtopia dialer, the other side can hear no echo while I get good audio quality. Apologies in advance for what may be a dumb question - but does this statement represent the conclusion of your team's work on audio issues (buzz/echo/hiss etc.)? Or is there further work ongoing? I very much hope the latter. At the very least, I feel we need a definitive and full description from your team of what the issues are, and the best available solutions (hardware and/or software) for them. If some of those solutions are version (a5, a6, ...) dependent, then they must include precise instructions on how an Openmoko user can determine which version they have. Once that description is available, either you or someone else can turn it into some kind of code or package, so that we can all take advantage of it. I know there is already a lot of google-able data on this, but in my view this is not useful even for an experienced user/programmer, as - it is all reported anecdotally and subjectively - there is simply too much of it to digest. So the detailed status needs to come from your team. I also assume (hope!) that you must have equipment specifically for detecting and measuring such audio effects, so I expect you can do a much better job of optimizing whatever needs to be optimized than all of us enthusiasts who don't have that equipment. Best wishes, Neil ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: auxlaunch ver 0.6
On Sunday 30 November 2008 23:24:07 Al Iasid wrote: Here's info on an update to auxlaunch, (finger-friendly app launcher and window switcher). Download at [1] and wiki page at [2]. Version 0.6 changes include: [...] Sounds interesting, would you care to mention which distro it is for? From the screen shots it looks like ASU, but it would be nice to know for sure. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Compatible earphones ...
On Monday 01 December 2008, Marcel wrote: Am Monday 01 December 2008 13:00:15 schrieb [EMAIL PROTECTED]: William Kenworthy [EMAIL PROTECTED] writes: Just broke my freerunners original headset. Is there a list of compatible models? - not much thats useful on the wiki that Ive been able to find Just that some Nokia smartphone models will work ... Looking more for a headset rather than the original earbuds. BillK Try to keep the broken headset around anyway. It can be useful to solder a headphone jack to it so you can use whatever headphones you like with it. The 2.5mm 4-pole plug seems hard to come by. And please add your results to [1] when you've got something working! :) [1] http://wiki.openmoko.org/wiki/Headset The pinout appears to be the same as the Blackberry Pearl too, but I haven't tried any headsets. I've added this to the wiki. Assuming it's correct the Shure MPA-2A would be worth a try. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: SD boot freeze, hang at boot time, why ?
Am Montag, den 01.12.2008, 03:15 +0100 schrieb Maelvon HAWK: Testing the Marian solution, I've modified the NAND boot, added the sleep 2; but on NAND boot it say now : boot Failed to mount ext2 filesystem... ** Bad ext2 partition or disk - mmc 1:1 ** Wrong image format for bootm command ERROR: can't get kernel image! /boot Hi Maelvon, from a distance I would guess the filesystem on your first partition (/dev/mmcblk0p1) is vfat and not ext2. Have a close look at the configure-uboot.sh, check the line with rootfstype=... from the first entry (after bootcmd=...). It should read (change it to): rootfstype=vfat hackable1.org requires a fat partition for the first partition. Debian on FR in contrast has discontinued booting from fat [1]. As the configure-uboot.sh was written for Debian on FR [2] the script does not honor vfat boot partitions. See [1] for discussion (follow the links to the Debian issue tracker and the smartphone-userland ML). regards, Marian [1] http://git.debian.org/?p=pkg-fso/files.git;a=commitdiff;h=6b1a3a1e217859ec9eb7ddf4d0ccdfe73275572a [2] http://wiki.debian.org/DebianOnFreeRunner ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [debian] sources
;-) ...i was searching something more stable only for fso because of this annoiyng no gps fix issue that i got after the update two weeks ago... thanks a lot for your answer! d On Mon, Dec 1, 2008 at 9:32 PM, Joachim Breitner [EMAIL PROTECTED] wrote: Hi, Am Montag, den 01.12.2008, 20:56 +0100 schrieb Davide Scaini: deb http://ftp2.de.debian.org/debian unstable main deb http://ftp2.de.debian.org/debian experimental main deb http://pkg-fso.alioth.debian.org/debian unstable main is it possible to have something less dangerous for everyday life? ;-) thanks You can of course install Debian stable on your FreeRunner, but it won't contain any OpenMoko-specific software. And I wouldn't consider unstabe exactly dangerous – I'm using it since over 6 years on my work machine. Greetings, Joachim -- Joachim nomeata Breitner Debian Developer [EMAIL PROTECTED] | ICQ# 74513189 | GPG-Keyid: 4743206C JID: [EMAIL PROTECTED] | http://people.debian.org/~nomeatahttp://people.debian.org/%7Enomeata ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [debian] sources
Hi, Am Montag, den 01.12.2008, 22:38 +0100 schrieb Davide Scaini: ;-) ...i was searching something more stable only for fso because of this annoiyng no gps fix issue that i got after the update two weeks ago... thanks a lot for your answer! the old versions of packages can be fetched manually from http://pkg-fso.alioth.debian.org/debian/pool/. Some people have asked or a unstable/stable repository switch, but there is not enough stable software to warrant that :-) (And not enough manpower...) Greetings, Joachim -- Joachim nomeata Breitner Debian Developer [EMAIL PROTECTED] | ICQ# 74513189 | GPG-Keyid: 4743206C JID: [EMAIL PROTECTED] | http://people.debian.org/~nomeata signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [debian] sources
ha ha thank you so much... i tried to manually downgrade to previous versions of fso but maybe ther're not more on the experimental branch when substituted with the newer version... thank you so much! d On Mon, Dec 1, 2008 at 10:57 PM, Joachim Breitner [EMAIL PROTECTED]wrote: Hi, Am Montag, den 01.12.2008, 22:38 +0100 schrieb Davide Scaini: ;-) ...i was searching something more stable only for fso because of this annoiyng no gps fix issue that i got after the update two weeks ago... thanks a lot for your answer! the old versions of packages can be fetched manually from http://pkg-fso.alioth.debian.org/debian/pool/. Some people have asked or a unstable/stable repository switch, but there is not enough stable software to warrant that :-) (And not enough manpower...) Greetings, Joachim -- Joachim nomeata Breitner Debian Developer [EMAIL PROTECTED] | ICQ# 74513189 | GPG-Keyid: 4743206C JID: [EMAIL PROTECTED] | http://people.debian.org/~nomeatahttp://people.debian.org/%7Enomeata ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Optimization team update (11/23 ~ 11/29)
I'll reflash tonight and update, and investigate some of the other problems as well. I need a phone so I've gone back to 2008.9 until tonight :) Saving images makes it so much more flash friendly! I dont think its fault, as the cow mooed quite fine before I updated. It was really a hit at work - seeing the 40-60yr old IT staff fascinated by it! - they are old enough to remember the original - my kids dont, so it sails straight by :( BillK On Mon, 2008-12-01 at 13:29 +, Thomas White wrote: On Mon, 01 Dec 2008 22:22:28 +0900 William Kenworthy [EMAIL PROTECTED] wrote: openmoocow (old version) started once out of three tries - left me at a grey screen otherwise. This is really my fault, due to a combination of MooCow's architecture in that version and the accelerometer driver behaviour. Try the newer version - it should work much better. Tom ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community -- William Kenworthy [EMAIL PROTECTED] Home in Perth! ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Optimization team update (11/23 ~ 11/29)
Thanks John, I'll reflash back to it tonight and provide feedback. If its not volume, I'll raise a bug if I can figure out the cause. I am a bit cautious of generalising this instance as I upgraded from a 2008.9 that has had bits from FDOM and elsewhere dropped into it. BillK On Mon, 2008-12-01 at 22:08 +0800, John Lee wrote: On Mon, Dec 01, 2008 at 10:22:28PM +0900, William Kenworthy wrote: ... Tried a test call - no audio :( thanks for the feedback! that sounds like #2140. have you tried to tune up the volume ? ... ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [QTEXTENDED] Very loud noise on (some) incoming calls
Hi, I had this issue only once : during a call I wanted to toggle some of the options (headset or headphone I don't remember) on. Had this loud noise and...rebooted. Never tried again. cheers 2008/12/2 Olivier Migeot [EMAIL PROTECTED] On Mon, Dec 1, 2008 at 4:51 PM, Warren Baird [EMAIL PROTECTED] wrote: I'm also using QTE 4.4.2, and I get this behaviour consistently after I configure a gprs internet connection. On Saturday I noticed it for the first time without trying to configure a gprs connection - but I'm not sure what triggered it. I normally try to reboot every couple of days, but hadn't in a while... It was fine after a reboot... I guess you just need to pretend the FR is a windows box and reboot it every couple of days... :-) Well, thanks for your answer, at least I'm not alone :) I can state the GPRS connection isn't the (only) reason, for I never configured any on my phone. Rebooting is a quick-fix, but without knowing how often one should do it, it's kinda pointless :/ Regards, -- Olivier M. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community -- Harald Zophon Zophoniasson www.zophon.net ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: OpenMooCow 0.2
Joachim Breitner [EMAIL PROTECTED] wrote: Nice. Is your git tree publicly available? Here you go, sorry for the wait: http://www.srcf.ucam.org/~taw27/openmoko/openmoocow/openmoocow.git Could you let me know if there are any problems with the current tip of 'master' on Thinkpad? It's working fine on my Freerunner here. If there are no problems, I'll release that as version 0.3 sometime next week. I'd like to wait just a little longer to see if any more installation problems with the .ipk arise, to avoid another awkward intermediate release like this time. Thanks for all your help, Tom ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: SD boot freeze, hang at boot time, why ?
Marian Flor a écrit :
Am Montag, den 01.12.2008, 03:15 +0100 schrieb Maelvon HAWK:
Testing the Marian solution, I've modified the NAND boot, added the
sleep 2; but on NAND boot it say now :
boot
Failed to mount ext2 filesystem...
** Bad ext2 partition or disk - mmc 1:1 **
Wrong image format for bootm command
ERROR: can't get kernel image!
/boot
Hi Maelvon,
from a distance I would guess the filesystem on your first partition
(/dev/mmcblk0p1) is vfat and not ext2.
Have a close look at the configure-uboot.sh, check the line with
rootfstype=... from the first entry (after bootcmd=...).
It should read (change it to): rootfstype=vfat
hackable1.org requires a fat partition for the first partition.
Debian on FR in contrast has discontinued booting from fat [1].
As the configure-uboot.sh was written for Debian on FR [2] the script
does not honor vfat boot partitions. See [1] for discussion (follow the
links to the Debian issue tracker and the smartphone-userland ML).
regards,
Marian
[1]
http://git.debian.org/?p=pkg-fso/files.git;a=commitdiff;h=6b1a3a1e217859ec9eb7ddf4d0ccdfe73275572a
[2] http://wiki.debian.org/DebianOnFreeRunner
Thanks Mariam,
You put me on the right way, I've forgot to change the ext2load mmc
to fatload with the rootfstype=vfat. So now it works with vfat.
But I've now a :
'''
kernel panic -not syncing: VFS: unable to mount root fs on
unknow-block(179,2)
'''
So with NOR, I've a :
'''
s3c2410_udc:debufs dir creation failed
'''
But Hackable:1 boot, and with NAND in vfat, I've a kernel panic
If I've put a vfat as rootfstype in NAND, what's the difference with the
original NOR u-boot ?
I'm a bit lost :-)
'''
diff ./configure-uboot-FAT.sh ./configure-uboot-EXT2.sh
38c38
rootfstype=vfat root=/dev/mmcblk0p2 rootdelay=5;
---
rootfstype=ext2 root=/dev/mmcblk0p2 rootdelay=5;
41c41
fatload mmc 1 0x3200 ${sd_image_name};
---
ext2load mmc 1 0x3200 ${sd_image_name};
'''
Maelvon
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: Android rootfs image?
Jeroen van de Nieuwenhof wrote: I installed Android on my Freerunner a few weeks ago, but changed back to Qt-Extended later. Now i want to install Android again but the rootfs image isnt available anymore at http://people.openmoko.org/sean_mcneil/ . I guess this is because the mp3 patent issue. Are there other images of Android available at the moment? A new image is coming at: http://people.openmoko.org/sean_mcneil/androidfs.jffs2 More from Sean's words in devel list: I am uploading a new rootfs.jffs as I type. It will take a few hours with my slow connection :( The issue with patents is causing great pain. Android is setup to either build with all of Packet Videos opencore, or to eliminate it. If eliminated, then the media playback and record cannot work as it uses Packet Video in a JNI interface. Building a partial opencore library is also quite difficult. I can't just eliminate particular codecs as they are static libraries with lots of dependencies. So, media handling is broken at the moment. You will see that it tells you in logcat it is out of memory, but that is just a bogus error. I am still working to fix it. Bye! -- Treviño's World - Life and Linux http://www.3v1n0.net/ ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
RE: [QTEXTENDED] Very loud noise on (some) incoming calls
I have this issue every so often as well. The weird thing is when the loud noise happens, the speaker phone is active as well (I didn't activate it, it answers with the speaker). Date: Tue, 2 Dec 2008 12:25:52 +1300 From: [EMAIL PROTECTED] To: community@lists.openmoko.org Subject: Re: [QTEXTENDED] Very loud noise on (some) incoming calls Hi, I had this issue only once : during a call I wanted to toggle some of the options (headset or headphone I don't remember) on. Had this loud noise and...rebooted. Never tried again. cheers 2008/12/2 Olivier Migeot [EMAIL PROTECTED] On Mon, Dec 1, 2008 at 4:51 PM, Warren Baird [EMAIL PROTECTED] wrote: I'm also using QTE 4.4.2, and I get this behaviour consistently after I configure a gprs internet connection. On Saturday I noticed it for the first time without trying to configure a gprs connection - but I'm not sure what triggered it. I normally try to reboot every couple of days, but hadn't in a while... It was fine after a reboot... I guess you just need to pretend the FR is a windows box and reboot it every couple of days... :-) Well, thanks for your answer, at least I'm not alone :) I can state the GPRS connection isn't the (only) reason, for I never configured any on my phone. Rebooting is a quick-fix, but without knowing how often one should do it, it's kinda pointless :/ Regards, -- Olivier M. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community -- Harald Zophon Zophoniasson www.zophon.net _ ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Optimization team update (11/23 ~ 11/29)
On Mon, Dec 01, 2008 at 02:06:34PM +0800, John Lee wrote: | * must remove 'ro' in kernel boot parameter if you use sd boot. At the moment Qi has ro boot everywhere by default, is this restriction just a temporary workaround for something? I think it's related to Olv's new boot scripts. I have rough idea about why but this can be better explained by him. It is a bug in the script if SD card is not re-mounted as rw. Could you send me the output of /proc/mounts when booting from SD card? -- Regards, olv ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Optimization team update (11/23 ~ 11/29)
On Mon, Dec 01, 2008 at 05:31:37PM +0100, Andreas Fischer wrote: Hi John, All, Just upgraded from 2008.9. Things to mention: - Boot time decreased. A lot! Thumbs up and a great Thank you for that :) - Also, startup time for applications (dialer) seems to have decreased. - As mentioned elsewhere, Enlightenment configuration was reset to not show the spanner and as the settings utility is unusable and the phone tends to suspend after 31 seconds, it is pretty unusable until one switches Enlightenment themes according to http://wiki.openmoko.org/wiki/Keyboard_Toggle (bottom of the page). sorry about the settings problem. we fixed multiple problems yesterday (see https://docs.openmoko.org/trac/ticket/2148). there was a really strange line in local.conf saying EXTENDPE = , which will cause a lot of problems. I have no idea who put that in... there used to be a wrench and qwerty button enabled theme, and now raster's illume default theme (illume-theme-illume, illume-config-illume) provides the same functionalities with a very different look. OM's theme will remain as it is like our designer wants it to be. you are free to switch between these two though, by setting it inside /etc/enlightenment/default_profile. - John - Even after disabling suspend I am having problems. In particular I am now experiencing WSoD even after screen blank (probably bug #2115: https://docs.openmoko.org/trac/ticket/2115 ). I suppose I need to disable screen blank too for now? Nevertheless, even though there are problems it's good to see progress. Keep up the good work. Regards, Andreas John Lee wrote: Dear Community, As Sushama (our new testing team member) indicated in http://lists.openmoko.org/pipermail/devel/2008-November/003493.html , we won't have a release in Nov. Currently the testing team is going to do a full test on the latest testing image. It has all the goodies we did and a lot of improvements over Om2008.9, so please try it and report any error you find. Upgrade howto: From Om2008.9 it's recommanded to upgrade with the following steps: sed -i -e 's%Om2008.8%testing%' /etc/opkg/*.conf /etc/init.d/xserver-nodm stop screen -DR opkg update opkg -force-overwrite upgrade # (please ans Y to all questions) # (the sshd (dropbear) will restart, so you need to reconnect and do # 'screen -DR' again) opkg upgrade shutdown -r now To get the fastest boot time you also need to remove the following packages: opkg remove task-base-nfs task-base-smbfs task-base-bluetooth \ task-base-usbgadget avahi-daemon avahi-autoipd blueprobe \ usb-gadget-mode portmap exquisite exquisite-theme-freerunner \ exquisite-themes Known issues: * GTK redraw problem * some obsolete kernel modules still left in system * must remove 'ro' in kernel boot parameter if you use sd boot. * will purge your incompatible e config, so you might need to set stuffs like suspend time again. Echo: Since there are different hw versions out there (a5, a6, a7), it's impossible to provide one alsa state file that suits all models. However, it seems you can always find appropriate values for your neo. My way is to adjust control.4 Speaker Playback Volume in /usr/share/openmoko/scenarios/gsmhandset.state the max value is 127, 95 works best on my a5. With volume level 3 or 4 in qtopia dialer, the other side can hear no echo while I get good audio quality. Team update: Tick helped to put his touchscreen improvement into stable-tracking, he will work on opkg internals next. Olv moved to look into kernel and fso. Erin will try bluetooth. Julian is working on the GTK redraw issue, please help him out. Jeremy will fix some qtopia bugs and keep working on suspend/resume issues. Regards, John ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Compatible earphones ...
Have to find something first - thinking bluetooth may be better. BillK On Mon, 2008-12-01 at 19:19 +0100, Marcel wrote: Am Monday 01 December 2008 13:00:15 schrieb [EMAIL PROTECTED]: William Kenworthy [EMAIL PROTECTED] writes: Just broke my freerunners original headset. Is there a list of compatible models? - not much thats useful on the wiki that Ive been able to find Just that some Nokia smartphone models will work ... Looking more for a headset rather than the original earbuds. BillK Try to keep the broken headset around anyway. It can be useful to solder a headphone jack to it so you can use whatever headphones you like with it. The 2.5mm 4-pole plug seems hard to come by. And please add your results to [1] when you've got something working! :) [1] http://wiki.openmoko.org/wiki/Headset -- Marcel ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Optimization team update (11/23 ~ 11/29)
On Mon, Dec 01, 2008 at 12:18:36AM +0300, Paul Fertser wrote: Andy Green [EMAIL PROTECTED] writes: Somebody in the thread at some point said: | Hi, | | Andy Green [EMAIL PROTECTED] writes: | For example some advice for Jeremy about suspend / resume issues | would be don't waste your time doing any suspend / resume work on | 2.6.24 kernel, only on andy-tracking. | | I'm very sorry to jump in this thread. But this advice of yours is | so much surprising! It implicitly suggests that Jeremy might be unaware of | the fact that every sane person knows for like 2 months. Do i Every sane person :-) No a lot of people are still using 2.6.24, all the distros are shipping it, it is in a branch called stable, it's not nuts if somebody tries to work on it. A lot of people are using, sure. But all the real work is done on *-tracking, it was obvious long ago from the commits, from the discussions, from the letter you posted earlier with the clear explanation about every branch's purpose. If he already knows it then fine, but people have been targeting stable in the last weeks for stuff that needs to be done on 2.6.28. That is strange. If they read the kernel list, then they already know what's going known and where you're heading. If they don't, how can they do kernel development then? Out of the context, in isolation? Just like samsung with their huge outdated patchsets, that can never be accepted upstream and therefore can be considered being dead before they born? | understand it right? How can it be possible at all? Everybody's so | excited about this Optimization team and you say they might | waste some time just because they don't lurk on -kernel mailing list? | | No offence meant, but that is sooo strange... I fear I've missed your point... John Lee wrote that two folks in Taiwan are going to be working specifically on kernel stuff... ''Olv moved to look into kernel and fso. ... Jeremy will fix some qtopia bugs and keep working on suspend/resume issues.'' I write to suggest they might get advantage if they coordinate kernel work on the kernel list -- at least we might not duplicate work on the same thing and there is a pretty fair amount of knowledge about Openmoko suspend / resume stuff on that list. What's sooo strange about that? Oh, you seem to be repeating the same thing you said earlier just to explain to me what's going on. I'm sorry for wasting your time. I think i understand you. The problem is that i'm not a native speaker and i tend to construct too complex sentences even in my native language. What i'm trying to explain is that i see it as plain obvious that anybody who wants to work on a kernel stuff should coordinate their efforts on the kernel list. That anybody targeting fixing bugs in suspend/resume knows about 2.6.24 deficiences long time ago. What you said to Jeremy sounded to me like: Hey, don't cross the street on red light, you might get hit by a car and die, you know. I was surprised that you treat a kernel developer from the optimization team like a child. If he is not experienced in kernel development why then didn't he ask you what kind of help was needed and decided to choose a task himself? And why the optimization team is still trying to fix bugs in Qtopia and derivitaves? Let Nokia do their work, if they really want to. Wouldn't it be better for the optimization team to hack on FSO or at least (as they are in Taiwan, that should be easy for them) get those bloody 100uF capacitors in place to finally provide the users with a decent bass? I don't want to sound too harsh to the optimization team. I just don't see them being public enough, coordinating their efforts with the main developers (of FSO and kernel) enough, going forward enough. I'm just afraid that they are somewhat like that mythical interface design department that never publicly communicates and demands technical nonsense from the real developers. (btw, i still remember the idea of taking a screenshot before suspending, oh boy, that was a bad sign from the optimization team) Hi, For now, I am working on fixing some qtopia stuff, to see if I can fix some bugs for later release, as well I would like to look into some kernel stuff. Ya, Andy has informed me that I should watch and work with andy-tracking branch long time ago. I know that. though I am not a skilled kernel guy. The same time I am indeed reading kernel mail list and logs to catch up with. It will take me more time. Thanks your suggestion giving and thanks Andy. I am trying testing suspend/resume recursively with a script, using werner's wkalrm. If anything I get or any plan, anyway I will talk on kernl list, let it be more public. Regards, - Jeremy No personal offense meant. -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:[EMAIL PROTECTED]
Google analytic records of November
Dear Documentation team, and Community: I update wiki google analytic records last month , you can check here. http://wiki.openmoko.org/wiki/Wiki_statistic_numbers#November.2C_2008 Feel free to let me know , if any kind of number you want .I can export and update it on wiki. Brenda ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Optimization team update (11/23 ~ 11/29)
On Mon, Dec 01, 2008 at 12:18:36AM +0300, Paul Fertser wrote: And why the optimization team is still trying to fix bugs in Qtopia and derivitaves? Let Nokia do their work, if they really want to. Wouldn't it be better for the optimization team to hack on FSO or at least (as they are in Taiwan, that should be easy for them) get those bloody 100uF capacitors in place to finally provide the users with a decent bass? Because people still need to use Om2008 based distro until the software release of gta03. Also, I have pointed out qtopia issues will be of lower priority before. I don't want to sound too harsh to the optimization team. I just don't see them being public enough, coordinating their efforts with the main developers (of FSO and kernel) enough, going forward enough. In the beginning of this thread I wrote we are going to become more involved with fso and kernel, but please understand what you think we should do may not be the same as what we are going to do and what we were asked to do. I'm just afraid that they are somewhat like that mythical interface design department that never publicly communicates and demands technical nonsense from the real developers. (btw, i still remember the idea of taking a screenshot before suspending, oh boy, that was a bad sign from the optimization team) Thanks for your worrying. No personal offense meant. Non taken. Regards, John ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [debian] sources
You can of course install Debian stable on your FreeRunner, but it won’t contain any OpenMoko-specific software. I'm running fso-pkg (unstable) alongside plain Debian testing. Stefan ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Optimization team update (11/23 ~ 11/29)
On Mon, Dec 01, 2008 at 09:29:48PM +, Neil Jerram wrote: 2008/11/30 John Lee [EMAIL PROTECTED]: Echo: Since there are different hw versions out there (a5, a6, a7), it's impossible to provide one alsa state file that suits all models. However, it seems you can always find appropriate values for your neo. My way is to adjust control.4 Speaker Playback Volume in /usr/share/openmoko/scenarios/gsmhandset.state the max value is 127, 95 works best on my a5. With volume level 3 or 4 in qtopia dialer, the other side can hear no echo while I get good audio quality. Apologies in advance for what may be a dumb question - but does this statement represent the conclusion of your team's work on audio issues (buzz/echo/hiss etc.)? Or is there further work ongoing? No, it's not the conclusion. We will keep working on that. I just described how I get the best out from the current sw/hw. I very much hope the latter. At the very least, I feel we need a definitive and full description from your team of what the issues are, and the best available solutions (hardware and/or software) for them. If some of those solutions are version (a5, a6, ...) dependent, then they must include precise instructions on how an Openmoko user can determine which version they have. Once that description is available, either you or someone else can turn it into some kind of code or package, so that we can all take advantage of it. Okay, I will think about this. I think the only real limitation here is we cannot ask everyone to do the soldering by him/her self, other then that, any software based solution is possible. Let me dig this deeper with the kernel and hw people. - John I know there is already a lot of google-able data on this, but in my view this is not useful even for an experienced user/programmer, as - it is all reported anecdotally and subjectively - there is simply too much of it to digest. So the detailed status needs to come from your team. I also assume (hope!) that you must have equipment specifically for detecting and measuring such audio effects, so I expect you can do a much better job of optimizing whatever needs to be optimized than all of us enthusiasts who don't have that equipment. Best wishes, Neil ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
