Re: Optimization team update (11/23 ~ 11/29)
arne anka wrote: [...] "Echo" reacts to some tweaking in alsa and maybe Calypso firmware option selection, I guess this turn up in rootfs images as best it can. >>> OK, but do you need to be so imprecise about this? What can't there >>> be a definitive solution? > > because the echo is caused only partially (if at all) by hardware. > especially gsm 1800 providers like e-plus in germany have been reported as > echo prone. > additionally people reported different experiences depending on their > location in time and space. > and last but not least: nobody knews what exactly N0187 is doing, and if > it will live trough firmware updates, since it is not documented. With echo problems varying so much, maybe the definite solution is to have an advanced setting, with options such as "no echo cancel", "undocumented N0187", and whatever other options there are. A sane default, and those who disagree just set something else they like. Just like suspend timeout which doesn't have a definitive solution either. Helge Hafting ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Optimization team update (11/23 ~ 11/29)
yes joerg has a DRAFT version of the SOP for the buzz fix rework of A5/A6. Not everybody has the buzz issue. 1. It's a draft. 2. We need to have some independent test of the SOP arne anka wrote: "buzz / echo / hiss"... no software change can fix buzz. It's baked into the hardware and you will have to do fairly extreme meddling with your soldering iron to impact it. >>> Thanks, I hadn't seen that so clearly stated before! (i.e. that buzz >>> is known to be 100% a hardware issue). > > probably since everyone expects everyone else to know it :-) > it was a hot topic some months ago, then someone (jörg?) came up with the > definite statement that it is hw related. > since then we're all waiting for working and more or less easy diy fix -- > which seems to be reached now. > >> weird though .. as I never experienced buzz in my calls (although I >> have to admit I didn't make more than 10 calls max uptill now) > > plug in the wired headset ... > "Echo" reacts to some tweaking in alsa and maybe Calypso firmware option selection, I guess this turn up in rootfs images as best it can. >>> OK, but do you need to be so imprecise about this? What can't there >>> be a definitive solution? > > because the echo is caused only partially (if at all) by hardware. > especially gsm 1800 providers like e-plus in germany have been reported as > echo prone. > additionally people reported different experiences depending on their > location in time and space. > and last but not least: nobody knews what exactly N0187 is doing, and if > it will live trough firmware updates, since it is not documented. > > since echo is a very complex issue, there are more then just one solution > more or less working for more or less people ... > > ___ > 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)
Am 08.12.2008 um 13:38 schrieb Joseph Reeves: > GTK support seems mildly improved in the testing release, but I'm > still having big troubles with it. Note, that relatively simple GTK > apps, such as TangoGPS work without issue. > > We're running a complex GTK app: http://gvsigmobileonopenmoko.wordpress.com/ > > It works perfectly on 2007.2, but on 2008.x releases it suffers from > multiple problems; layouting and stability seem to the big ones. It is > improved when running on the latest testing release, but still not up > to the standard of GTK applications on 2007.2. > > We were promised that we wouldn't need to worry about Openmoko moving > away from GTK as the latest releases would still run GTK applications. > However performance is clearly below an acceptable level. Yes, please file bugs. Please also attach the versions of cairo, gtk+, glib, pango from Om2007.2 and Om2008.8. Did you try to use a different theme engine? Is that changing the performance? z. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Optimization team update (11/23 ~ 11/29)
GTK support seems mildly improved in the testing release, but I'm still having big troubles with it. Note, that relatively simple GTK apps, such as TangoGPS work without issue. We're running a complex GTK app: http://gvsigmobileonopenmoko.wordpress.com/ It works perfectly on 2007.2, but on 2008.x releases it suffers from multiple problems; layouting and stability seem to the big ones. It is improved when running on the latest testing release, but still not up to the standard of GTK applications on 2007.2. We were promised that we wouldn't need to worry about Openmoko moving away from GTK as the latest releases would still run GTK applications. However performance is clearly below an acceptable level. I will be filing bugs ASAP and would be very interested in hearing comments from others. If anyone would like a copy of the gvSIG Mobile ipk for testing, please let me know. Thanks, Joseph 2008/11/30 John Lee <[EMAIL PROTECTED]>: > 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)
On Sunday 07 December 2008, Neil Jerram wrote: > 2008/12/2 Andy Green <[EMAIL PROTECTED]>: > > "buzz / echo / hiss"... no software change can fix buzz. It's baked > > into the hardware and you will have to do fairly extreme meddling with > > your soldering iron to impact it. > > Thanks, I hadn't seen that so clearly stated before! (i.e. that buzz > is known to be 100% a hardware issue). > > > "Echo" reacts to some tweaking in alsa and maybe Calypso firmware option > > selection, I guess this turn up in rootfs images as best it can. > > OK, but do you need to be so imprecise about this? What can't there > be a definitive solution? It depends partly on what you mean by a definitive solution. If you mean "one alsa state file that everyone's happy with" it'll never happen because the 'correct' volume level is subjective and depends on ambient noise among other variables outside our control. If you mean something that's reasonable out of the box and only needs a small tweak of the volume then my experience is we have had it since the calypso echo suppression was enabled. It doesn't help that the echo suppression and noise reduction functions we need from the Calypso are undocumented. It seems there are some gain controls in the Calypso too. Some of us find that the echo suppression remains effective until a reboot while others report it only working for the first call, and we don't know the cause. There are several settings available for both echo suppression and noise reduction, and they have different audible characteristics. Generally the stronger the suppression the more audible its action. People don't agree on which ones sound acceptable, and which one you use can have a significant effect on the gain you can use before you start getting echo. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Optimization team update (11/23 ~ 11/29)
>> > "buzz / echo / hiss"... no software change can fix buzz. It's baked >> > into the hardware and you will have to do fairly extreme meddling >> > with your soldering iron to impact it. >> >> Thanks, I hadn't seen that so clearly stated before! (i.e. that buzz >> is known to be 100% a hardware issue). probably since everyone expects everyone else to know it :-) it was a hot topic some months ago, then someone (jörg?) came up with the definite statement that it is hw related. since then we're all waiting for working and more or less easy diy fix -- which seems to be reached now. > weird though .. as I never experienced buzz in my calls (although I > have to admit I didn't make more than 10 calls max uptill now) plug in the wired headset ... >> > "Echo" reacts to some tweaking in alsa and maybe Calypso firmware >> > option selection, I guess this turn up in rootfs images as best it >> > can. >> >> OK, but do you need to be so imprecise about this? What can't there >> be a definitive solution? because the echo is caused only partially (if at all) by hardware. especially gsm 1800 providers like e-plus in germany have been reported as echo prone. additionally people reported different experiences depending on their location in time and space. and last but not least: nobody knews what exactly N0187 is doing, and if it will live trough firmware updates, since it is not documented. since echo is a very complex issue, there are more then just one solution more or less working for more or less people ... ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Optimization team update (11/23 ~ 11/29)
On Sun, 7 Dec 2008 15:22:58 + "Neil Jerram" <[EMAIL PROTECTED]> wrote: > 2008/12/2 Andy Green <[EMAIL PROTECTED]>: > > > > "buzz / echo / hiss"... no software change can fix buzz. It's baked > > into the hardware and you will have to do fairly extreme meddling > > with your soldering iron to impact it. > > Thanks, I hadn't seen that so clearly stated before! (i.e. that buzz > is known to be 100% a hardware issue). weird though .. as I never experienced buzz in my calls (although I have to admit I didn't make more than 10 calls max uptill now) > > "Echo" reacts to some tweaking in alsa and maybe Calypso firmware > > option selection, I guess this turn up in rootfs images as best it > > can. > > OK, but do you need to be so imprecise about this? What can't there > be a definitive solution? weird again ... I had major echo issues (for the party calling me that is), but using %N0187 solved this in one go (I never tried the other at commands mentioned in another mail that should solve/minimize echo issues). Using alsa states influenced echo, but only because you in fact decrease the volume of the calling party. Even more strange is that this at-command doesn't seem an accepted solution but people try to stop echo in one or two at-commands at the modem initialization time, and that doesn't seem to work but still it continues to be the choosen path. I don't care that this at-command gets send on every call, as long as it eliminates echo. For me this is the definitive solution. Franky ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Optimization team update (11/23 ~ 11/29)
Oops... 2008/12/7 Neil Jerram <[EMAIL PROTECTED]>: > > OK, but do you need to be so imprecise about this? What can't there > be a definitive solution? "What" should have been "why". Neil ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Optimization team update (11/23 ~ 11/29)
2008/12/2 Andy Green <[EMAIL PROTECTED]>: > > "buzz / echo / hiss"... no software change can fix buzz. It's baked > into the hardware and you will have to do fairly extreme meddling with > your soldering iron to impact it. Thanks, I hadn't seen that so clearly stated before! (i.e. that buzz is known to be 100% a hardware issue). > "Echo" reacts to some tweaking in alsa and maybe Calypso firmware option > selection, I guess this turn up in rootfs images as best it can. OK, but do you need to be so imprecise about this? What can't there be a definitive solution? > "Hiss and Etc" I didn't hear about, but I don't think kernel or hardware > world can cover for any of it on existing device. Only button to push > in userspace world is optimization of echo I think we find, unless > "hiss" is somethng like bad channel selection in alsa world. I must admit that I've never heard the "hiss" either, so I don't know exactly what it means... but someone that I called a few days ago said there was a strong hiss on the line. (In retrospect, I should at least have tried calling again, as maybe it was just a line issue.) Regards, Neil ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Optimization team update (11/23 ~ 11/29)
2008/12/2 John Lee <[EMAIL PROTECTED]>: > On Mon, Dec 01, 2008 at 09:29:48PM +, Neil Jerram wrote: >> >> 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. That's good to know; thanks. > 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. I haven't done any soldering for years. But I will risk doing it - or get someone to do it for me - if it is sufficiently clear exactly what needs doing, and the probability is high enough that it will solve the problem. Of course, I also see that there will be some who completely rule that out. So basically I agree with you. The key thing is to have a crystal clear description of the options. Regards, Neil ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Optimization team update (11/23 ~ 11/29)
Thanks Jake. I reviewed the SOP yesterday and Werner had a look at it as well. There is a tiny bit of clean up ( spelling etc) and a couple little details. ( arrows on the photos) Also, I really would like to have somebody external to Openmoko "test" the SOP by actually doing it. Maybe even make a Youtube vid. But, I won't hold up the document for that. I expect we can go live with the document sometime next week. Bug me if you want a Pre release of the doc and would like to suggest changes for clarity I'll see what I can do. Steve Jakob wrote: > Thanks Steve for this little insight. > As the mod doesn't seem that hard to do, I'm looking forward to my > Freerunner for christmas (regardless if its A7 or a not yet reworked > A6 :) ). > > Jake > > On Thu, Dec 4, 2008 at 1:46 PM, Steve Mosher <[EMAIL PROTECTED]> wrote: >> Hi, >> >> Joerg went over the change for a5/a6 with me the other night. >> Over the next few days I'll drive to get an SOP published for >> the change. But for now I'll just explain it in words. The modification >> should work for both a5&a6. It consists of: >> >> 1. Removing the front cover. >> 2. Changing a resistor ( in some cases this is not necessary) >> 3. Adding a Cap. >> >> Steve ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Optimization team update (11/23 ~ 11/29)
John Lee wrote: > On Fri, Dec 05, 2008 at 10:28:48AM +0100, Andreas Fischer wrote: >> Hi All, >> >> During today's upgrade I encountered the following error: >> >> * ERROR: The following packages conflict with openmoko-phoneprofile-data: >> * qtopia-phone-x11-profile-data * >> >> How should I proceed? Uninstall one of these? > > remove qtopia-phone-x11-profile-data and install > openmoko-phoneprofile-data That seemed to work. Thank you. > openmoko-phoneprofile-data is already in Om2008.9 so I wonder why you > have qtopia-phone-x11-profile-data installed. I have no idea, actually. Maybe some remnant of an update? I certainly didn't install it on purpose... Regards, Andreas >> 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 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Optimization team update (11/23 ~ 11/29)
On Fri, Dec 05, 2008 at 10:28:48AM +0100, Andreas Fischer wrote: > Hi All, > > During today's upgrade I encountered the following error: > > * ERROR: The following packages conflict with openmoko-phoneprofile-data: > * qtopia-phone-x11-profile-data * > > How should I proceed? Uninstall one of these? remove qtopia-phone-x11-profile-data and install openmoko-phoneprofile-data openmoko-phoneprofile-data is already in Om2008.9 so I wonder why you have qtopia-phone-x11-profile-data installed. > > 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: Optimization team update (11/23 ~ 11/29)
Hi All, During today's upgrade I encountered the following error: * ERROR: The following packages conflict with openmoko-phoneprofile-data: * qtopia-phone-x11-profile-data * How should I proceed? Uninstall one of these? 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 Steve for this little insight. As the mod doesn't seem that hard to do, I'm looking forward to my Freerunner for christmas (regardless if its A7 or a not yet reworked A6 :) ). Jake On Thu, Dec 4, 2008 at 1:46 PM, Steve Mosher <[EMAIL PROTECTED]> wrote: > Hi, > > Joerg went over the change for a5/a6 with me the other night. > Over the next few days I'll drive to get an SOP published for > the change. But for now I'll just explain it in words. The modification > should work for both a5&a6. It consists of: > > 1. Removing the front cover. > 2. Changing a resistor ( in some cases this is not necessary) > 3. Adding a Cap. > > Steve ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Optimization team update (11/23 ~ 11/29)
Hi, Joerg went over the change for a5/a6 with me the other night. Over the next few days I'll drive to get an SOP published for the change. But for now I'll just explain it in words. The modification should work for both a5&a6. It consists of: 1. Removing the front cover. 2. Changing a resistor ( in some cases this is not necessary) 3. Adding a Cap. Steve Jakob wrote: > On Tue, Dec 2, 2008 at 9:42 PM, Andy Green <[EMAIL PROTECTED]> wrote: > >> "buzz / echo / hiss"... no software change can fix buzz. It's baked >> into the hardware and you will have to do fairly extreme meddling with >> your soldering iron to impact it. > > Would it be better to wait until A7 is out and then buy a Freerunner? > How hard is it to do the component change on a A6? > > Jake > > ___ > 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)
Jakob a écrit : On Tue, Dec 2, 2008 at 9:42 PM, Andy Green <[EMAIL PROTECTED]> wrote: "buzz / echo / hiss"... no software change can fix buzz. It's baked into the hardware and you will have to do fairly extreme meddling with your soldering iron to impact it. Would it be better to wait until A7 is out and then buy a Freerunner? How hard is it to do the component change on a A6? Jake Since it's a harware bug, which impact the intended use of the device, will it be covered by the warranty? K- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Optimization team update (11/23 ~ 11/29)
Ticket #2157 Would be nice if anyone else is seeing this to pipe up too - starting to feel its just me ... BillK On Wed, 2008-12-03 at 21:54 +0800, John Lee wrote: > > 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 > > ... > > > > Ive been using this for a couple of days now and have some more > items: > > > > SMS messages are still being held up. If the phone is suspended, it > > will wake but never indicate an SMS has been received. They only > show > > up when rebooting the phone, or mostly on restarting the xserver. > There > > are a few bugs on this like 1766, but thats not exactly the same and > was > > supposed to be fixed in testing - would this fix come in as part of > the > > upgrade? > > This doesn't seem like #1766, and I've just received a sms in > suspend... Could you file a ticket? Please attach the following if > possible: > > * upgrade from Om2008.9 or flashed daily image ? > * output of 'opkg list_installed' > * logread > * the modified qtopia config file, if any. > -- 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 Tue, Dec 2, 2008 at 9:42 PM, Andy Green <[EMAIL PROTECTED]> wrote: > "buzz / echo / hiss"... no software change can fix buzz. It's baked > into the hardware and you will have to do fairly extreme meddling with > your soldering iron to impact it. Would it be better to wait until A7 is out and then buy a Freerunner? How hard is it to do the component change on a A6? Jake ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Optimization team update (11/23 ~ 11/29)
On Wed, Dec 03, 2008 at 05:50:50PM +0900, William Kenworthy wrote: > 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 > ... > > Ive been using this for a couple of days now and have some more items: > > SMS messages are still being held up. If the phone is suspended, it > will wake but never indicate an SMS has been received. They only show > up when rebooting the phone, or mostly on restarting the xserver. There > are a few bugs on this like 1766, but thats not exactly the same and was > supposed to be fixed in testing - would this fix come in as part of the > upgrade? This doesn't seem like #1766, and I've just received a sms in suspend... Could you file a ticket? Please attach the following if possible: * upgrade from Om2008.9 or flashed daily image ? * output of 'opkg list_installed' * logread * the modified qtopia config file, if any. > The wifi icon is still dodgy - comes on when wifi started, never stops > when wifi is stopped. That's #1742 and it's still open. Testing repo will switch to new kernel, and wifi driver will be in once it's ready. > The GSM icon stays at one bar (or is it a "!"), never moves, even > before/after registration. Can't reproduce... I need to read your attachments. - John > Other than the last, I though these issues were solved in testing, so > they might be upgrade issues. > > BillK ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Optimization team update (11/23 ~ 11/29)
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 ... Ive been using this for a couple of days now and have some more items: SMS messages are still being held up. If the phone is suspended, it will wake but never indicate an SMS has been received. They only show up when rebooting the phone, or mostly on restarting the xserver. There are a few bugs on this like 1766, but thats not exactly the same and was supposed to be fixed in testing - would this fix come in as part of the upgrade? The wifi icon is still dodgy - comes on when wifi started, never stops when wifi is stopped. The GSM icon stays at one bar (or is it a "!"), never moves, even before/after registration. Other than the last, I though these issues were solved in testing, so they might be upgrade issues. BillK ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Optimization team update (11/23 ~ 11/29)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: |> 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? "buzz / echo / hiss"... no software change can fix buzz. It's baked into the hardware and you will have to do fairly extreme meddling with your soldering iron to impact it. "Echo" reacts to some tweaking in alsa and maybe Calypso firmware option selection, I guess this turn up in rootfs images as best it can. "Hiss and Etc" I didn't hear about, but I don't think kernel or hardware world can cover for any of it on existing device. Only button to push in userspace world is optimization of echo I think we find, unless "hiss" is somethng like bad channel selection in alsa world. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkk1ncAACgkQOjLpvpq7dMoWVgCgiF4Bsh30L8k3oEZF1Me5peit gQ4An35b4aFzPmvddxScu6pFHmSIlsRQ =GXBl -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Optimization team update (11/23 ~ 11/29)
William Kenworthy wrote: > Thats it. I installed my favourite gsmhandset.state which made the mic > audio acceptable. Then I modified PhoneProfile.conf as per #2140 and > have audio again. > > I presume this fix (#2140) will appear in an update shortly? I guess, since the openmoko OE tree has been fixed... -- 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: Optimization team update (11/23 ~ 11/29)
On Tue, Dec 02, 2008 at 07:50:58PM +0900, William Kenworthy wrote: > On Mon, 2008-12-01 at 22:22 +0900, William Kenworthy wrote: > > Thanks, also I was bit too rushed. I shut down X which allowed me to > > > > > Fonts and widgets are far too large on apps like pythm, tangogps and the > > like. > > > ... > > Fixed by adding the gtkrc fix from FDOM > > Should I raise a bug for this - I think it is an old issue (as evidenced > by the fact that FDOM has had the fix for awhile) > > BillK Please do since I couldn't find it in trac. Here is the diff between the old gtkrc from moko-gtk-engine and the one from FDOM: $ diff -urN gtkrc /home/john/tmp/FDOMizer/fixes/gtkrc --- gtkrc 2008-10-30 18:42:30.0 +0800 +++ /home/john/tmp/FDOMizer/fixes/gtkrc 2008-10-19 16:12:35.0 +0800 @@ -12,6 +12,12 @@ gtk-button-images = 0 gtk-menu-images = 0 gtk-icon-sizes = "gtk-button=32,32:gtk-small-toolbar=48,48:gtk-large-toolbar=48,48" +gtk-font-name = "Sans 4" +gtk-icon-theme-name="openmoko-standard" +gtk-toolbar-icon-size = GTK_ICON_SIZE_SMALL_TOOLBAR + + + # Set the default gtk-color-scheme property gtk_color_scheme = "fg_color:#fff;bg_color:#333;base_color:#aaa;text_color:#000;selected_bg_color:#ff7d00;selected_fg_color:#000" @@ -182,10 +188,10 @@ } widget "*.mokosearchbutton" style "mokosearchbutton" -include "matchboxpanel" -include "openmoko-calculator" -include "openmoko-contacts" -include "openmoko-dialer" -include "openmoko-panel-plugins" -include "openmoko-mediaplayer" +include "/usr/share/themes/Moko/gtk-2.0/matchboxpanel" +include "/usr/share/themes/Moko/gtk-2.0/openmoko-calculator" +include "/usr/share/themes/Moko/gtk-2.0/openmoko-contacts" +include "/usr/share/themes/Moko/gtk-2.0/openmoko-dialer" +include "/usr/share/themes/Moko/gtk-2.0/openmoko-panel-plugins" + I don't have enough knowledge to comment on it. The second section seems strange to me though, because it assumes files will be installed to /usr/share/themes/Moko/gtk-2.0/ while this should really be decided by autotools. Could someone please review it? If it's okay I'm going to apply it to svn. - John ___ 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, 2008-12-01 at 22:22 +0900, William Kenworthy wrote: > Thanks, also I was bit too rushed. I shut down X which allowed me to > > Fonts and widgets are far too large on apps like pythm, tangogps and the > like. > ... Fixed by adding the gtkrc fix from FDOM Should I raise a bug for this - I think it is an old issue (as evidenced by the fact that FDOM has had the fix for awhile) BillK ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Optimization team update (11/23 ~ 11/29)
Thats it. I installed my favourite gsmhandset.state which made the mic audio acceptable. Then I modified PhoneProfile.conf as per #2140 and have audio again. I presume this fix (#2140) will appear in an update shortly? Thanks. 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: > > 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 hea
Re: Optimization team update (11/23 ~ 11/29)
Upgraded to 0.2 - works fine. 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)
On Tue, Dec 02, 2008 at 10:49:47AM +0100, Andreas Fischer wrote: > John Lee wrote: > > 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... > > Ah - that would probably also explain the frequent enlightenment crashes > I was going to complain about. I'll test with the new python-etk and see > how it goes from there. > > Thanks for your answer, > Andreas enlightenment crashes? sounds familiar https://docs.openmoko.org/trac/ticket/1767 I'm in a dilemma here. Either I have to put in a lot of resource to fix the software_16 engine, or I have to switch to software_x like Raster suggested and make everything slower. :( - John > > > > > 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 > >> ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Optimization team update (11/23 ~ 11/29)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | 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. Great, automated stress / regression testing of suspend will be a very welcome innovation (hopefully even the results will be welcome sometimes too :-) ) - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkk1BZYACgkQOjLpvpq7dMrDPwCeMx14nlQgRNBgr23QEsPBT0xW n8YAn3j6Ao0OEkmyTd8/Mj9D5VgYELBt =wwl3 -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Optimization team update (11/23 ~ 11/29)
John Lee wrote: > 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... Ah - that would probably also explain the frequent enlightenment crashes I was going to complain about. I'll test with the new python-etk and see how it goes from there. Thanks for your answer, Andreas > > 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 ___ 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
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: 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
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: 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)
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: 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)
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: 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: 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)
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: 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 see
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 > > >> > > >> _
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 > > >> > > >> __
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)
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 > > > > ___
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
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 Sun, Nov 30, 2008 at 06:56:28PM +, Andy Green wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Somebody in the thread at some point said: > > Hi John - > > | * some obsolete kernel modules still left in system > > If we didn't do it already, the packaged kernels need to move to having > /lib/modules path that is specific to the kernel device and build, > similar to what the ./build script does: > > /lib/modules/2.6.28-GTA02_andy-tracking_d0aa5acc0be7c573-mokodev/ > > The branch and hash stops any conflict about module versions, and the > device tag "GTA02" allows multiple kernels to be installed on the same > rootfs, so you can share the SD Card between GTA01 and GTA02 say, both > times with SD Card boot to the right kernel. Yup, but it won't make opkg remove the unnecessary modules. It's a problem that needs to be solved in OE. > | * 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. > | 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. > > Just a thought, it can be worth Olv and Jeremy bouncing what they're > planning on doing off the kernel list. 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. Thanks for the reminder. :) - John ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Optimization team update (11/23 ~ 11/29)
On Sun, Nov 30, 2008 at 01:32:20PM +, Rui Miguel Silva Seabra wrote:
> On Sun, Nov 30, 2008 at 07:50:22PM +0800, John Lee wrote:
> > 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.
>
> This is interesting, I have an a5 and the default value of FSO M4.1a:
>
> control.4 {
> comment.access 'read write'
> comment.type INTEGER
> comment.count 2
> comment.range '0 - 127'
> iface MIXER
> name 'Speaker Playback Volume'
> value.0 116
> value.1 116
> }
>
> Sometimes I ask people on the other side: do you hear echo? The answer
> has been no.
>
> Rui
116 was the old value I use before I updated the alsa state file from
FDOM. There was no/very little echo, but the other side always
complains they cannot hear me very well. I also feel the receiver
(handset speaker) is unnecessarily loud sometimes.
The new alsa state file uses 116, but boosts the mic path a little bit
more, so it solved the "can't hear me" problem while makes the echo
even easier to happen. With the new state file, 95 is the best value
for me because I can always make it louder if necessary with Tick's
volume bar in qtopia.
- John
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: Optimization team update (11/23 ~ 11/29)
On Sun, Nov 30, 2008 at 02:16:48PM +0100, Franky Van Liedekerke wrote: > On Sun, 30 Nov 2008 19:50:22 +0800 > John Lee <[EMAIL PROTECTED]> wrote: > > > 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. > > Does this mean the fix is only through alsa? So the fix mentioned here: > http://n2.nabble.com/FSO-M4---nice-GSM-sound-tp1486414p1518726.html > is not ok? Since that fix is the only real fix for my echo issues (and > it seems to come from 2008.8). > > Franky That fix is already in testing repo, maybe over 1 month now. However even with this patch there is still chance you can hear echo. Let's say A calls B, and B is using a neo with this fix. 1. The receiver (handset speaker) is loud enough and the mic is sensitive enough, so gsm won't turn off the mic. 2. A starts speaking right after B, but gsm needs a little time to turn off mic. In either case you can still here a little echo. Much better then before, of course, but still a little. I was talking about 1. in my previous post. - John ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Optimization team update (11/23 ~ 11/29)
On Sun, Nov 30, 2008 at 10:56:47PM +0100, Fabian Henze wrote: > On 30.11.2008 at 12:50:22, John Lee wrote: > > Since there are different hw versions out there (a5, a6, a7), it's > > impossible to provide one alsa state file that suits all models. > > Just a short question: What is a7? > Can you please update the wiki article about the GTA02 revisions? > > -- Fabian I think it's not shipped yet, so maybe it exists only inside openmoko. I don't know about the details. - John ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Optimization team update (11/23 ~ 11/29)
On 30.11.2008 at 12:50:22, John Lee wrote: > Since there are different hw versions out there (a5, a6, a7), it's > impossible to provide one alsa state file that suits all models. Just a short question: What is a7? Can you please update the wiki article about the GTA02 revisions? -- Fabian ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Optimization team update (11/23 ~ 11/29)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | 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 The fact is I don't know what Olv and Jeremy are planning on doing in the kernel because it hasn't appeared on the kernel list or anywhere else for me. But that's all... I have no problem with their experience level and will be interested to see what they're coming up with, and if I can help. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkkzCCgACgkQOjLpvpq7dMpopQCeNgUq6HhK1UOpUG44b9ltDZkm OesAnihKj1eUuuJCCfozUU2kqDFJDxk5 =kUyy -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Optimization team update (11/23 ~ 11/29)
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) No personal offense meant. -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:[EMAIL PROTECTED] ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Optimization team update (11/23 ~ 11/29)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 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. But there are multiple known issues with suspend / resume solved on 2.6.28 stuff and for sure unless they are solved first debugging suspend resume will be exercise in chasing one's tail. 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. | 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? - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkky+doACgkQOjLpvpq7dMo4GQCfSRrSFPE8WSACxUIgaXrBBzn6 C8wAn3nEoVN9VPjEMd9zQ2mukdo2D666 =1qaJ -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Optimization team update (11/23 ~ 11/29)
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 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... -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:[EMAIL PROTECTED] ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Optimization team update (11/23 ~ 11/29)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: Hi John - | * some obsolete kernel modules still left in system If we didn't do it already, the packaged kernels need to move to having /lib/modules path that is specific to the kernel device and build, similar to what the ./build script does: /lib/modules/2.6.28-GTA02_andy-tracking_d0aa5acc0be7c573-mokodev/ The branch and hash stops any conflict about module versions, and the device tag "GTA02" allows multiple kernels to be installed on the same rootfs, so you can share the SD Card between GTA01 and GTA02 say, both times with SD Card boot to the right kernel. | * 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? | 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. Just a thought, it can be worth Olv and Jeremy bouncing what they're planning on doing off the kernel list. 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. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkky4dwACgkQOjLpvpq7dMrSTACeNaM2tQ5kn+rvzlTJC0nD5N5L s8wAnAn/GDMCXyBN8ODnY2sq5XhheRn/ =/Ytn -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Optimization team update (11/23 ~ 11/29)
On Sun, Nov 30, 2008 at 07:50:22PM +0800, John Lee wrote:
> 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.
This is interesting, I have an a5 and the default value of FSO M4.1a:
control.4 {
comment.access 'read write'
comment.type INTEGER
comment.count 2
comment.range '0 - 127'
iface MIXER
name 'Speaker Playback Volume'
value.0 116
value.1 116
}
Sometimes I ask people on the other side: do you hear echo? The answer
has been no.
Rui
--
Hail Eris, Hack GNU/Linux!
Today is Prickle-Prickle, the 42nd day of The Aftermath in the YOLD 3174
+ No matter how much you do, you never do enough -- unknown
+ Whatever you do will be insignificant,
| but it is very important that you do it -- Gandhi
+ So let's do it...?
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: Optimization team update (11/23 ~ 11/29)
On Sun, 30 Nov 2008 19:50:22 +0800 John Lee <[EMAIL PROTECTED]> wrote: > 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. Does this mean the fix is only through alsa? So the fix mentioned here: http://n2.nabble.com/FSO-M4---nice-GSM-sound-tp1486414p1518726.html is not ok? Since that fix is the only real fix for my echo issues (and it seems to come from 2008.8). Franky ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Optimization team update (11/23 ~ 11/29)
Or one could create a statefiles-metapackage and make the user choose his model upon installation - or do this in package setup/configuration scripts... -- Marcel Am Sunday 30 November 2008 13:01:47 schrieb Yorick Moko: > great news, > > but can't the opkg upgrade detect which hw revision we have and > install the best alsa state file? > afterall, good call quality is something almost everybody wants > > y > > On Sun, Nov 30, 2008 at 12:50 PM, John Lee <[EMAIL PROTECTED]> 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
Re: Optimization team update (11/23 ~ 11/29)
great news, but can't the opkg upgrade detect which hw revision we have and install the best alsa state file? afterall, good call quality is something almost everybody wants y On Sun, Nov 30, 2008 at 12:50 PM, John Lee <[EMAIL PROTECTED]> 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
