Re: [om2009-r4] Warren's Settings Worked for Me (was Re: Om2009 testing release 4)
Am Mo 8. Juni 2009 schrieb Warren Baird: complained that I sounded a bit muffled, so I reset it to the 101 (same as gsmhandset-a7.state), and since then it seems pretty good - my wife has please notice: http://docs.openmoko.org/trac/ticket/2121#comment:3 gsmhandset-a7.state is deprecated! cheers jOERG signature.asc Description: This is a digitally signed message part. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [om2009-r4] Warren's Settings Worked for Me (was Re: Om2009 testing release 4)
Thanks, Joerg - I hadn't noticed that comment. Hmm - would it be possible to add a note at the top of the file itself indicating this? I found a post by you in the community list indicating that this was the 'real' state file to use, and so have been using it. I didn't think to check the comments on the associated issue. And frankly, my audio quality with it is better than with any of the other state files I've tried - much less buzz. Is it possible that the changes in the -a7 file reduce the impact of the buzz? I'm probably going to keep using it until I get the buzz fix operation performed. Warren On Tue, Jun 9, 2009 at 9:14 AM, Joerg Reisenweber jo...@openmoko.orgwrote: Am Mo 8. Juni 2009 schrieb Warren Baird: complained that I sounded a bit muffled, so I reset it to the 101 (same as gsmhandset-a7.state), and since then it seems pretty good - my wife has please notice: http://docs.openmoko.org/trac/ticket/2121#comment:3 gsmhandset-a7.state is deprecated! cheers jOERG -- Warren Baird - Photographer and Digital Artist http://www.synergisticimages.ca ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
initramfs (was: Re: Om2009 testing release 4)
Hi Kevin, Kevin Day wrote (ao): The initramfs must be pregenerated. The command to create the initramfs is: find . | cpio --quiet -H newc -o | gzip -9 -n /usr/src/boot-initrd.cpio.gz Place the initramfs into the kernel source tree, and then something like this config option should be used: CONFIG_INITRAMFS_SOURCE=boot-initrd.cpio.gz There is no need to create the initramfs. You can just have this in your kernel config: CONFIG_INITRAMFS_SOURCE=/home/user/initramfs The /home/user/initramfs directory gets included in the initramfs during kernel build. With kind regards, Sander -- Humilis IT Services and Solutions http://www.humilis.net ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [om2009-r4] Warren's Settings Worked for Me (was Re: Om2009 testing release 4)
Am Do 4. Juni 2009 schrieb William Ray Yeager: A critical friend of mine who has mocked my purchase of an unfinished phone just told me that our connection was as good as a landline! I followed Warren's advice below and lowered control.5 to 80 (I'm naturally conservative) which has (so far) completely removed the previously unbearable buzz my friend had observed on the other end of the conversation. Wow. Now I might not need to solder in a new capacitor! For the demi-newbie: Open /usr/share/openmoko/scenarios/gsmhandset.state Scroll down to control.5 and in that section change the line under 'Mono Playback Volume' from value 110 to value 80. Save file. Call OM skeptic. Gloat. Warren said: I've always had people complain that they got a lot of static when they called me - I thought I had the buzz problem in fact. I just spent the time to figure out how to use alsamixer to tweak things, and if I set control.5 (Mono Playback Volume) to 83 from above 100 like I've seen in other gsmhandset.state files (ranging from 100 to 110 seems normal), I get a perfectly clear signal on the other end. Another unconfirmed taletelling about Buzzfix by ALSA settings. Don't you think we checked this prior to coming up with a hw-rework after months and months of wrestling with this issue? /j signature.asc Description: This is a digitally signed message part. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [om2009-r4] Warren's Settings Worked for Me (was Re: Om2009 testing release 4)
Joerg Reisenweber wrote (ao): Am Do 4. Juni 2009 schrieb William Ray Yeager: A critical friend of mine who has mocked my purchase of an unfinished phone just told me that our connection was as good as a landline! I followed Warren's advice below and lowered control.5 to 80 (I'm naturally conservative) which has (so far) completely removed the previously unbearable buzz my friend had observed on the other end of the conversation. Wow. Now I might not need to solder in a new capacitor! For the demi-newbie: Open /usr/share/openmoko/scenarios/gsmhandset.state Scroll down to control.5 and in that section change the line under 'Mono Playback Volume' from value 110 to value 80. Save file. Call OM skeptic. Gloat. Warren said: I've always had people complain that they got a lot of static when they called me - I thought I had the buzz problem in fact. I just spent the time to figure out how to use alsamixer to tweak things, and if I set control.5 (Mono Playback Volume) to 83 from above 100 like I've seen in other gsmhandset.state files (ranging from 100 to 110 seems normal), I get a perfectly clear signal on the other end. Another unconfirmed taletelling about Buzzfix by ALSA settings. Don't you think we checked this prior to coming up with a hw-rework after months and months of wrestling with this issue? Joerg, I also tested this by lowering Mono to 72 with alsa-mixer on my A6 OM2009 Test4 after reading Warrens mail, and I now no longer sound like sitting on a motor lawnmower during a call. Maybe this is something different than the Buzz Issue, but it improves sounds for the other party a lot. This btw is in The Netherlands. After reading that less than 5% of the owners are hit in practice by the Buzz Issue, I was pretty surprised to be one of them. But now it seems the noise is not due to the Buzz Issue? With kind regards, Sander -- Humilis IT Services and Solutions http://www.humilis.net ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [om2009-r4] Warren's Settings Worked for Me (was Re: Om2009 testing release 4)
Joerg, I also tested this by lowering Mono to 72 with alsa-mixer on my A6 OM2009 Test4 after reading Warrens mail, and I now no longer sound like sitting on a motor lawnmower during a call. Maybe this is something different than the Buzz Issue, but it improves sounds for the other party a lot. I've experienced that on some settings the background noise of my environment (=cars / computer fan / air conditioning / ...) is amplified a lot when I'm silent and the person I'm talking to can hear it. It isn't easy to recognice what's the source of the noise but I'd say there's some tunign to do to make this work. So I don't think it's the actual buzz but amplifying the environment. r -- | risto h. kurppa | risto at kurppa dot fi | http://risto.kurppa.fi ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [om2009-r4] Warren's Settings Worked for Me (was Re: Om2009 testing release 4)
Am Mo 8. Juni 2009 schrieb openm...@humilis.net: Joerg Reisenweber wrote (ao): Am Do 4. Juni 2009 schrieb William Ray Yeager: A critical friend of mine who has mocked my purchase of an unfinished phone just told me that our connection was as good as a landline! I followed Warren's advice below and lowered control.5 to 80 (I'm naturally conservative) which has (so far) completely removed the previously unbearable buzz my friend had observed on the other end of the conversation. Wow. Now I might not need to solder in a new capacitor! For the demi-newbie: Open /usr/share/openmoko/scenarios/gsmhandset.state Scroll down to control.5 and in that section change the line under 'Mono Playback Volume' from value 110 to value 80. Save file. Call OM skeptic. Gloat. Warren said: I've always had people complain that they got a lot of static when they called me - I thought I had the buzz problem in fact. I just spent the time to figure out how to use alsamixer to tweak things, and if I set control.5 (Mono Playback Volume) to 83 from above 100 like I've seen in other gsmhandset.state files (ranging from 100 to 110 seems normal), I get a perfectly clear signal on the other end. Another unconfirmed taletelling about Buzzfix by ALSA settings. Don't you think we checked this prior to coming up with a hw-rework after months and months of wrestling with this issue? Joerg, I also tested this by lowering Mono to 72 with alsa-mixer on my A6 OM2009 Test4 after reading Warrens mail, and I now no longer sound like sitting on a motor lawnmower during a call. Maybe this is something different than the Buzz Issue, but it improves sounds for the other party a lot. This btw is in The Netherlands. After reading that less than 5% of the owners are hit in practice by the Buzz Issue, I was pretty surprised to be one of them. But now it seems the noise is not due to the Buzz Issue? reducing mic gain and/or mic volume might cause some of the many sound improvement circuits involved in carriers' exchange (here: half duplex echo cancellation, kind of a two-way noise gate) to cut out buzz during periods of no voice transmitted. Nevertheless the S/N ratio *during talking* (S=your voice, N=buzz) can NOT be changed by alsa settings any way whatsoever. So this change of control.5 may improve some of the subjective audio sensation for far end, only if you got slight buzz that becomes unnoticeable during actual voice. Severe buzz rendering voice illegible can NOT be cured this way, not even a little bit. btw you can get same result (without lowering volume of your voice for far end, and without relying on carrier's/far-end's EC meassures) by setting AT%N noise gate value of Calypso to a level that effectively stops buzz during periods of no voice (aka silence) Official recommendation is: If you got Buzz issue, try to get bigC-buzzfix. cheers jOERG signature.asc Description: This is a digitally signed message part. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [om2009-r4] Warren's Settings Worked for Me (was Re: Om2009 testing release 4)
Am Mo 8. Juni 2009 schrieb Risto H. Kurppa: Joerg, I also tested this by lowering Mono to 72 with alsa-mixer on my A6 OM2009 Test4 after reading Warrens mail, and I now no longer sound like sitting on a motor lawnmower during a call. Maybe this is something different than the Buzz Issue, but it improves sounds for the other party a lot. I've experienced that on some settings the background noise of my environment (=cars / computer fan / air conditioning / ...) is amplified a lot when I'm silent and the person I'm talking to can hear it. It isn't easy to recognice what's the source of the noise but I'd say there's some tunign to do to make this work. So I don't think it's the actual buzz but amplifying the environment. r See my other post wrt EC and calypso noisegate. Basically I'm telling your story there. cheers jOERG signature.asc Description: This is a digitally signed message part. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [om2009-r4] Warren's Settings Worked for Me (was Re: Om2009 testing release 4)
Please note the hardware revisions A5 and A6 have a hardware defect that is being recalled. To determine your hardware revision http://wiki.openmoko.org/wiki/Neo_FreeRunner_Hardware#Distinguishing_hardware_revisions I was notified by the vendor I purchased my freerunner from. Figured I would share this info. On Mon, Jun 8, 2009 at 10:29 AM, Joerg Reisenweber jo...@openmoko.orgwrote: Am Mo 8. Juni 2009 schrieb Risto H. Kurppa: Joerg, I also tested this by lowering Mono to 72 with alsa-mixer on my A6 OM2009 Test4 after reading Warrens mail, and I now no longer sound like sitting on a motor lawnmower during a call. Maybe this is something different than the Buzz Issue, but it improves sounds for the other party a lot. I've experienced that on some settings the background noise of my environment (=cars / computer fan / air conditioning / ...) is amplified a lot when I'm silent and the person I'm talking to can hear it. It isn't easy to recognice what's the source of the noise but I'd say there's some tunign to do to make this work. So I don't think it's the actual buzz but amplifying the environment. r See my other post wrt EC and calypso noisegate. Basically I'm telling your story there. cheers jOERG ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support -- Paul Email - pault...@gmail.com There were moments when he looked on evil simply as a mode through which he could realize his conception of the beautiful. Oscar Wilde - The Picture of Dorian Gray ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [om2009-r4] Warren's Settings Worked for Me (was Re: Om2009 testing release 4)
Hi Joerg, I certainly don't mean to downplay the research you did - I was just trying to explain the experiences I've had. When I set control.5 to about 85 I no longer heard a buzz when I called myself on a phone - A few people complained that I sounded a bit muffled, so I reset it to the 101 (same as gsmhandset-a7.state), and since then it seems pretty good - my wife has complained once about some intermittent minor buzz, but I've had a number of phone conversations where people said I sounded fine. I've still seen varying opinions on these mailing lists ranging from 'only 5% of people need the buzz fix' to 'everyone with an A5 or A6 needs the buzz fix'. Is the official line that everyone with an A5 or A6 would benefit from the buzz fix? Warren On Mon, Jun 8, 2009 at 9:49 AM, Joerg Reisenweber jo...@openmoko.orgwrote: Warren said: I've always had people complain that they got a lot of static when they called me - I thought I had the buzz problem in fact. I just spent the time to figure out how to use alsamixer to tweak things, and if I set control.5 (Mono Playback Volume) to 83 from above 100 like I've seen in other gsmhandset.state files (ranging from 100 to 110 seems normal), I get a perfectly clear signal on the other end. Another unconfirmed taletelling about Buzzfix by ALSA settings. Don't you think we checked this prior to coming up with a hw-rework after months and months of wrestling with this issue? /j ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support -- Warren Baird - Photographer and Digital Artist http://www.synergisticimages.ca ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [om2009-r4] Warren's Settings Worked for Me (was Re: Om2009 testing release 4)
I've still seen varying opinions on these mailing lists ranging from 'only 5% of people need the buzz fix' to 'everyone with an A5 or A6 needs the buzz fix'. they're not really varying -- it's like learning to swim: if you are absolutely sure, you'll never get into deep water, there's no need to spend time learning how to swim. but if you're unsure, you better do it. it's the same with the buzz fix: if you don't experience it and if you are absolutely sure, the location and conditions your fr works under will never change, no need to fix. technically, though, the buzz is there and you might experience it when you expect it the least. so, if you got the opportunity to get the fix applied, use it -- better safe than sorry. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Om2009 testing release 4
On June 5, 2009 02:31:16 am Patryk Benderz wrote: Looks like these: http://downloads.openmoko.org/distro/testing/NeoFreerunner/ are the same images i downloaded last time, May 21st. Am i looking for them at right place? The testing images haven't changed but the unstable ones have had quite a bit of work done. Angus ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Om2009 testing release 4
On Tue, Jun 2, 2009 at 9:50 AM, Al Johnson openm...@mazikeen.demon.co.uk wrote: On Tuesday 02 June 2009, Robin Paulson wrote: 2009/6/2 Al Johnson openm...@mazikeen.demon.co.uk: On Tuesday 26 May 2009, Robin Paulson wrote: there's no incentive i can see to stay with uboot You probably don't have 4 different distros on your SD then ;-) no, i don't. but it doesn't look like it will be long before qi can do multi-boot http://wiki.openmoko.org/wiki/Qi#Boot_Menu It's been done already - there was a thread about building the minimal kernel and rootfs, and using it to kexec into the one you really want to boot. Unfortunately that takes up another partition that I just don't have spare due to the kernel limitation on partitions in mmcblk devices, and android's thirst for partitions. This could be worked around too, but as I already have a working uboot setup there doesn't seem much point. I've nothing against Qi, but in my case uboot is the better tool for the job. What one could do is create an initramfs and build it directly into the kernel. The small rootfs would exist with the boot kernel on any desired partition (say partition 0), taking up no more partitions than already used. The initramfs must be pregenerated. The command to create the initramfs is: find . | cpio --quiet -H newc -o | gzip -9 -n /usr/src/boot-initrd.cpio.gz Place the initramfs into the kernel source tree, and then something like this config option should be used: CONFIG_INITRAMFS_SOURCE=boot-initrd.cpio.gz It's relatively easy to tell when the initrd makes it into the kernel, just look at its size! -- Kevin Day ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Om2009 testing release 4
On Wednesday 03 June 2009, Kevin Day wrote: On Tue, Jun 2, 2009 at 9:50 AM, Al Johnson openm...@mazikeen.demon.co.uk wrote: On Tuesday 02 June 2009, Robin Paulson wrote: 2009/6/2 Al Johnson openm...@mazikeen.demon.co.uk: On Tuesday 26 May 2009, Robin Paulson wrote: there's no incentive i can see to stay with uboot You probably don't have 4 different distros on your SD then ;-) no, i don't. but it doesn't look like it will be long before qi can do multi-boot http://wiki.openmoko.org/wiki/Qi#Boot_Menu It's been done already - there was a thread about building the minimal kernel and rootfs, and using it to kexec into the one you really want to boot. Unfortunately that takes up another partition that I just don't have spare due to the kernel limitation on partitions in mmcblk devices, and android's thirst for partitions. This could be worked around too, but as I already have a working uboot setup there doesn't seem much point. I've nothing against Qi, but in my case uboot is the better tool for the job. What one could do is create an initramfs and build it directly into the kernel. The small rootfs would exist with the boot kernel on any desired partition (say partition 0), taking up no more partitions than already used. That's one of several possible workarounds, but it's not very helpful given that the partitions tend to get reformatted and have a new tarball extracted over them fairly often. The workarounds all involve extra work for little gain. One thing that would fix it would be if Qi would check the last partition, which may be a partition that is outside the kernel partition limit. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
[om2009-r4] Warren's Settings Worked for Me (was Re: Om2009 testing release 4)
A critical friend of mine who has mocked my purchase of an unfinished phone just told me that our connection was as good as a landline! I followed Warren's advice below and lowered control.5 to 80 (I'm naturally conservative) which has (so far) completely removed the previously unbearable buzz my friend had observed on the other end of the conversation. Wow. Now I might not need to solder in a new capacitor! For the demi-newbie: Open /usr/share/openmoko/scenarios/gsmhandset.state Scroll down to control.5 and in that section change the line under 'Mono Playback Volume' from value 110 to value 80. Save file. Call OM skeptic. Gloat. Warren said: I've always had people complain that they got a lot of static when they called me - I thought I had the buzz problem in fact. I just spent the time to figure out how to use alsamixer to tweak things, and if I set control.5 (Mono Playback Volume) to 83 from above 100 like I've seen in other gsmhandset.state files (ranging from 100 to 110 seems normal), I get a perfectly clear signal on the other end. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Om2009 testing release 4
On Tuesday 26 May 2009, Robin Paulson wrote: there's no incentive i can see to stay with uboot You probably don't have 4 different distros on you SD then ;-) ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Om2009 testing release 4
On Tuesday 02 June 2009 13:04:13 Al Johnson wrote: On Tuesday 26 May 2009, Robin Paulson wrote: there's no incentive i can see to stay with uboot You probably don't have 4 different distros on you SD then ;-) +1 ;) ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Om2009 testing release 4
2009/6/2 Al Johnson openm...@mazikeen.demon.co.uk: On Tuesday 26 May 2009, Robin Paulson wrote: there's no incentive i can see to stay with uboot You probably don't have 4 different distros on your SD then ;-) no, i don't. but it doesn't look like it will be long before qi can do multi-boot http://wiki.openmoko.org/wiki/Qi#Boot_Menu ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Om2009 testing release 4
2009/6/2 Robin Paulson robin.paul...@gmail.com: 2009/6/2 Al Johnson openm...@mazikeen.demon.co.uk: On Tuesday 26 May 2009, Robin Paulson wrote: there's no incentive i can see to stay with uboot You probably don't have 4 different distros on your SD then ;-) no, i don't. but it doesn't look like it will be long before qi can do multi-boot http://wiki.openmoko.org/wiki/Qi#Boot_Menu Quoting from that paragraph: - Therefore Qi does NOT provide a boot menu. This should rather be implemented by a minimal Kernel, initramfs and menu system. Qi will not initialize any video, that's why it needs to boot a mini-kernel which then provides a boot menu where a user can select from which partition he wants to boot. I ask you, what was wrong with u-boot, which already did that without that mini-kernel? It cannot be speeding up the boot-process, because the loading time for Qi or u-boot cannot be much different, and when the kernel is loaded and started, both loaders vanish. I'm sure you can add a kernel cmdline-param -quiet to u-boot too. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Om2009 testing release 4
The major reason for Qi's existence is maintainability. U-Boot has a problem with all drivers for different HW being copied from the kernel tree. When the kernel is updated/patched, the fixes don't automagically appear in U-Boot. Qi instead try to do as little as possible to be HW independant. Then you can use a mini-kernel to make a boot menu. In this way you get all the fixes from upstream development without the need of any manual copy/paste and possible further debugging to get it to work. From a strict user perspective, Qi don't give any more features. However it's a lot easier to make new features for Qi, since you can use normal development tools and don't have to learn the U-Boot way. If X is installed for the boot-menu, it can use a lot of eye-candy! (although probably way to heavy) /Micael On Tue, Jun 2, 2009 at 3:54 PM, Joachim Ott jo.o...@googlemail.com wrote: 2009/6/2 Robin Paulson robin.paul...@gmail.com: 2009/6/2 Al Johnson openm...@mazikeen.demon.co.uk: On Tuesday 26 May 2009, Robin Paulson wrote: there's no incentive i can see to stay with uboot You probably don't have 4 different distros on your SD then ;-) no, i don't. but it doesn't look like it will be long before qi can do multi-boot http://wiki.openmoko.org/wiki/Qi#Boot_Menu Quoting from that paragraph: - Therefore Qi does NOT provide a boot menu. This should rather be implemented by a minimal Kernel, initramfs and menu system. Qi will not initialize any video, that's why it needs to boot a mini-kernel which then provides a boot menu where a user can select from which partition he wants to boot. I ask you, what was wrong with u-boot, which already did that without that mini-kernel? It cannot be speeding up the boot-process, because the loading time for Qi or u-boot cannot be much different, and when the kernel is loaded and started, both loaders vanish. I'm sure you can add a kernel cmdline-param -quiet to u-boot too. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Om2009 testing release 4
On Tuesday 02 June 2009, Robin Paulson wrote: 2009/6/2 Al Johnson openm...@mazikeen.demon.co.uk: On Tuesday 26 May 2009, Robin Paulson wrote: there's no incentive i can see to stay with uboot You probably don't have 4 different distros on your SD then ;-) no, i don't. but it doesn't look like it will be long before qi can do multi-boot http://wiki.openmoko.org/wiki/Qi#Boot_Menu It's been done already - there was a thread about building the minimal kernel and rootfs, and using it to kexec into the one you really want to boot. Unfortunately that takes up another partition that I just don't have spare due to the kernel limitation on partitions in mmcblk devices, and android's thirst for partitions. This could be worked around too, but as I already have a working uboot setup there doesn't seem much point. I've nothing against Qi, but in my case uboot is the better tool for the job. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Finding a recent U-Boot (Was: Om2009 testing release 4)
On Mon, Jun 01, 2009 at 04:50:12PM +1200, Robin Paulson wrote: this is more about predicting where qi will go in future, than where it is now. and various people from om have talked about qi being the way forward. i imagine there will be no more significant changes to uboot from here onwards, whereas qi will steadily improve. i might be wrong Those same people also don't work for OM any more, so the amount of time they have available for qi work could be very limited. Andy said he'd keep working on qi[1], but we haven't seen any of it yet. Likewise we haven't yet seen much of what I said I'd work on for U-Boot[2][3] either. Judge by what people _actually_ do rather than what they say they'll do. [1] https://lists.openmoko.org/pipermail/openmoko-kernel/2009-March/009584.html [2] https://lists.openmoko.org/pipermail/openmoko-kernel/2009-April/009827.html [3] https://lists.openmoko.org/pipermail/openmoko-kernel/2009-April/010007.html -- Rask Ingemann Lambertsen Danish law requires addresses in e-mail to be logged and stored for a year ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Om2009 testing release 4
I'm starting to think that this must be the case. I've always had people complain that they got a lot of static when they called me - I thought I had the buzz problem in fact. I just spent the time to figure out how to use alsamixer to tweak things, and if I set control.5 (Mono Playback Volume) to 83 from above 100 like I've seen in other gsmhandset.state files (ranging from 100 to 110 seems normal), I get a perfectly clear signal on the other end. I'll see if people now complain that I'm too quiet... but it's a lot better than the static. I'd suggest that *everyone* try out alsamixer - I just called my phone with a landline, and then fired it up alsamixer and experiemented with what alsamixer called 'Mono' until the static went away... Wish I'd figured that out months ago... Warren On Fri, May 29, 2009 at 8:45 PM, Petr Vanek van...@penguin.cz wrote: The link to the statefile produces a lot of static and echo. I've tweaked mine to a usable level. It is attached to this email. This file still needs work. Hmm.. interesting, I have no problems with it.. I wonder if the FR's are unique in this sense..? i can only speak for myself - we have to FRs in our family and yes they really are unique in this sense - one needed this state file tweaking to put volume lower, another to set volume up higher Petr ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support -- Warren Baird - Photographer and Digital Artist http://www.synergisticimages.ca ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Finding a recent U-Boot (Was: Om2009 testing release 4)
On Tue, May 26, 2009 at 07:55:31PM +1200, Robin Paulson wrote: i think the critical thing is that you are using a *recent* version of whichever bootloader, be it uboot or qi http://wiki.openmoko.org/wiki/Om2009#Installing Unfortunately, the U-Boot download link points to an ancient (8 months old) version of U-Boot. The latest U-Boot is here: http://downloads.openmoko.org/distro/experimental/NeoFreerunner/ that said, i'm sticking with qi, and development there looks much more active. Not much difference: U-Boot: Two commits in the last two months. [1] qi: Three commits in the last two months. [2] [1] http://git.openmoko.org/?p=u-boot.git;a=shortlog;h=refs/heads/stable [2] http://git.openmoko.org/?p=qi.git;a=shortlog;h=refs/heads/master there's no incentive i can see to stay with uboot Other than being able to flash a new boot loader. :-) -- Rask Ingemann Lambertsen Danish law requires addresses in e-mail to be logged and stored for a year ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Finding a recent U-Boot (Was: Om2009 testing release 4)
On Sun, May 31, 2009 at 18:18, Rask Ingemann Lambertsen r...@sygehus.dk wrote: Other than being able to flash a new boot loader. :-) With Qi you're still able to flash a new bootloader (unless you have gta01 without debug board :P) ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Finding a recent U-Boot (Was: Om2009 testing release 4)
2009/6/1 Rask Ingemann Lambertsen r...@sygehus.dk: Unfortunately, the U-Boot download link points to an ancient (8 months old) version of U-Boot. The latest U-Boot is here: http://downloads.openmoko.org/distro/experimental/NeoFreerunner/ ah, good you found it. i didn't realise that link was broken that said, i'm sticking with qi, and development there looks much more active. Not much difference: U-Boot: Two commits in the last two months. [1] qi: Three commits in the last two months. [2] well, statistics can be deceptive. you're not wrong, but: u-boot 2 commits this year qi: 50+ commits this year of course, my stats could be deceptive too, and not tell the whole story. and they don't. this is more about predicting where qi will go in future, than where it is now. and various people from om have talked about qi being the way forward. i imagine there will be no more significant changes to uboot from here onwards, whereas qi will steadily improve. i might be wrong [1] http://git.openmoko.org/?p=u-boot.git;a=shortlog;h=refs/heads/stable [2] http://git.openmoko.org/?p=qi.git;a=shortlog;h=refs/heads/master there's no incentive i can see to stay with uboot Other than being able to flash a new boot loader. :-) eh? i'm happy with qi, my fr is working well (aside from wifi), and can update qi when i need to. i was careful all the way through what i said to include what 'i' am doing, rather than what you should do cheers ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Om2009 testing release 4
r, The link to the statefile produces a lot of static and echo. I've tweaked mine to a usable level. It is attached to this email. This file still needs work. On Thu, May 28, 2009 at 11:58 PM, Risto H. Kurppa ri...@kurppa.fi wrote: I myself am using http://www.kurppa.fi/freerunner/config_files/gsmhandset.state - but I guess the one installed by default should work too (not sure if it's the same nowadays..). When on call, AUX changes the speaker volume (20-40-60-80-100%). Using level over 80 might cause some echo. r -- | risto h. kurppa | risto at kurppa dot fi | http://risto.kurppa.fi ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support -- Paul Email - pault...@gmail.com There were moments when he looked on evil simply as a mode through which he could realize his conception of the beautiful. Oscar Wilde - The Picture of Dorian Gray gsmhandset.state Description: Binary data ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Om2009 testing release 4
On Fri, May 29, 2009 at 10:29 PM, Paul pault...@gmail.com wrote: r, The link to the statefile produces a lot of static and echo. I've tweaked mine to a usable level. It is attached to this email. This file still needs work. Hmm.. interesting, I have no problems with it.. I wonder if the FR's are unique in this sense..? r -- | risto h. kurppa | risto at kurppa dot fi | http://risto.kurppa.fi ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Om2009 testing release 4
The link to the statefile produces a lot of static and echo. I've tweaked mine to a usable level. It is attached to this email. This file still needs work. Hmm.. interesting, I have no problems with it.. I wonder if the FR's are unique in this sense..? i can only speak for myself - we have to FRs in our family and yes they really are unique in this sense - one needed this state file tweaking to put volume lower, another to set volume up higher Petr ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Om2009 testing release 4
Can someone please post a usable state file, the edits on the link http://docs.openmoko.org/trac/changeset/4968 were already in the state file. Please help, My friends will not talk to me! On Thu, May 28, 2009 at 12:51 AM, Risto H. Kurppa ri...@kurppa.fi wrote: On Wed, May 27, 2009 at 8:12 PM, Paul pault...@gmail.com wrote: Thanks Warren. Before I go home and try this out, does anyone know if the echo patch is applied to 2009? Yes it is, it's been in since OM2008.12 or so.. r -- | risto h. kurppa | risto at kurppa dot fi | http://risto.kurppa.fi ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support -- Paul Email - pault...@gmail.com There were moments when he looked on evil simply as a mode through which he could realize his conception of the beautiful. Oscar Wilde - The Picture of Dorian Gray ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Om2009 testing release 4
I myself am using http://www.kurppa.fi/freerunner/config_files/gsmhandset.state - but I guess the one installed by default should work too (not sure if it's the same nowadays..). When on call, AUX changes the speaker volume (20-40-60-80-100%). Using level over 80 might cause some echo. r -- | risto h. kurppa | risto at kurppa dot fi | http://risto.kurppa.fi ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Om2009 testing release 4
On Tue, May 26, 2009 at 6:16 PM, Chris Jenks ch...@jenks.us wrote: On Tue, 26 May 2009, Alexander Shulgin wrote: Finally it works for me after qi reflash. :) -- Alex I thought it was working too until I got a couple calls. The callers hung up after not being able to hear me at all. Isn't anyone else having this problem? Well, I only mean it booted to X. :) I didn't have enough time to check the calls. Firing an SMS worked smoothly, though. -- Alex ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Om2009 testing release 4
Thanks Warren. Before I go home and try this out, does anyone know if the echo patch is applied to 2009? Thanks. On Wed, May 27, 2009 at 1:01 PM, Warren Baird wjba...@alumni.uwaterloo.cawrote: I found the message I followed - the suggestion was to basically undo http://docs.openmoko.org/trac/changeset/4968 - I just edited the file, and changed all of the green lines back to the red lines... Warren On Tue, May 26, 2009 at 4:44 PM, Paul pault...@gmail.com wrote: Can your provide the state file or a link to it? Thanks. On Tue, May 26, 2009 at 12:58 PM, Warren Baird wjba...@alumni.uwaterloo.ca wrote: I'm using TR4 - I had to tweak the gsmhandset.state file (as mentioned by someone else in a thread - I can't recall where right now - sorry). Without the tweak I was able to receive calls, but the audio quality was horrible - really bad background buzz. I am using u-boot - I upgraded it probably 6 months ago. Don't recall the version off-hand, but I can check if you need me to. Warren On Tue, May 26, 2009 at 11:16 AM, Chris Jenks ch...@jenks.us wrote: On Tue, 26 May 2009, Alexander Shulgin wrote: Finally it works for me after qi reflash. :) -- Alex I thought it was working too until I got a couple calls. The callers hung up after not being able to hear me at all. Isn't anyone else having this problem? I'm using the latest u-boot, kernel and root in testing, all dated May 21st, on a stock Freerunner, flashed to v11 of the GSM firmware. I suppose I can see if qi fixes it, but every time I try qi I get WSOD. Chris ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support -- Warren Baird - Photographer and Digital Artist http://www.synergisticimages.ca ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support -- Paul Email - pault...@gmail.com There were moments when he looked on evil simply as a mode through which he could realize his conception of the beautiful. Oscar Wilde - The Picture of Dorian Gray ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support -- Warren Baird - Photographer and Digital Artist http://www.synergisticimages.ca ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support -- Paul Email - pault...@gmail.com There were moments when he looked on evil simply as a mode through which he could realize his conception of the beautiful. Oscar Wilde - The Picture of Dorian Gray ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Om2009 testing release 4
On Wed, May 27, 2009 at 8:12 PM, Paul pault...@gmail.com wrote: Thanks Warren. Before I go home and try this out, does anyone know if the echo patch is applied to 2009? Yes it is, it's been in since OM2008.12 or so.. r -- | risto h. kurppa | risto at kurppa dot fi | http://risto.kurppa.fi ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Om2009 testing release 4
On Fri, May 22, 2009 at 7:07 PM, Alexander Shulgin alex.shul...@gmail.com wrote: Oh, silly me. I just realized I didn't reflash the boot loader. Will try a bit later. Finally it works for me after qi reflash. :) -- Alex ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Om2009 testing release 4
В Втр, 26/05/2009 в 10:11 +0300, Alexander Shulgin пишет: On Fri, May 22, 2009 at 7:07 PM, Alexander Shulgin alex.shul...@gmail.com wrote: Oh, silly me. I just realized I didn't reflash the boot loader. Will try a bit later. Finally it works for me after qi reflash. :) That's kind of scary - did I got it right that in order to use OM TR 4 I have to flash Qi instead of u-boot? best regards, Max. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Om2009 testing release 4
2009/5/26 Max m...@darim.com: В Втр, 26/05/2009 в 10:11 +0300, Alexander Shulgin пишет: On Fri, May 22, 2009 at 7:07 PM, Alexander Shulgin alex.shul...@gmail.com wrote: Oh, silly me. I just realized I didn't reflash the boot loader. Will try a bit later. Finally it works for me after qi reflash. :) That's kind of scary - did I got it right that in order to use OM TR 4 I have to flash Qi instead of u-boot? i think the critical thing is that you are using a *recent* version of whichever bootloader, be it uboot or qi http://wiki.openmoko.org/wiki/Om2009#Installing that said, i'm sticking with qi, and development there looks much more active. there's no incentive i can see to stay with uboot ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Om2009 testing release 4
On Tue, 26 May 2009, Alexander Shulgin wrote: Finally it works for me after qi reflash. :) -- Alex I thought it was working too until I got a couple calls. The callers hung up after not being able to hear me at all. Isn't anyone else having this problem? I'm using the latest u-boot, kernel and root in testing, all dated May 21st, on a stock Freerunner, flashed to v11 of the GSM firmware. I suppose I can see if qi fixes it, but every time I try qi I get WSOD. Chris ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Om2009 testing release 4
I'm using TR4 - I had to tweak the gsmhandset.state file (as mentioned by someone else in a thread - I can't recall where right now - sorry). Without the tweak I was able to receive calls, but the audio quality was horrible - really bad background buzz. I am using u-boot - I upgraded it probably 6 months ago. Don't recall the version off-hand, but I can check if you need me to. Warren On Tue, May 26, 2009 at 11:16 AM, Chris Jenks ch...@jenks.us wrote: On Tue, 26 May 2009, Alexander Shulgin wrote: Finally it works for me after qi reflash. :) -- Alex I thought it was working too until I got a couple calls. The callers hung up after not being able to hear me at all. Isn't anyone else having this problem? I'm using the latest u-boot, kernel and root in testing, all dated May 21st, on a stock Freerunner, flashed to v11 of the GSM firmware. I suppose I can see if qi fixes it, but every time I try qi I get WSOD. Chris ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support -- Warren Baird - Photographer and Digital Artist http://www.synergisticimages.ca ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Om2009 testing release 4
Can your provide the state file or a link to it? Thanks. On Tue, May 26, 2009 at 12:58 PM, Warren Baird wjba...@alumni.uwaterloo.cawrote: I'm using TR4 - I had to tweak the gsmhandset.state file (as mentioned by someone else in a thread - I can't recall where right now - sorry). Without the tweak I was able to receive calls, but the audio quality was horrible - really bad background buzz. I am using u-boot - I upgraded it probably 6 months ago. Don't recall the version off-hand, but I can check if you need me to. Warren On Tue, May 26, 2009 at 11:16 AM, Chris Jenks ch...@jenks.us wrote: On Tue, 26 May 2009, Alexander Shulgin wrote: Finally it works for me after qi reflash. :) -- Alex I thought it was working too until I got a couple calls. The callers hung up after not being able to hear me at all. Isn't anyone else having this problem? I'm using the latest u-boot, kernel and root in testing, all dated May 21st, on a stock Freerunner, flashed to v11 of the GSM firmware. I suppose I can see if qi fixes it, but every time I try qi I get WSOD. Chris ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support -- Warren Baird - Photographer and Digital Artist http://www.synergisticimages.ca ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support -- Paul Email - pault...@gmail.com There were moments when he looked on evil simply as a mode through which he could realize his conception of the beautiful. Oscar Wilde - The Picture of Dorian Gray ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Om2009 testing release 4
On Fri, 2009-05-22 at 19:07 +0300, Alexander Shulgin wrote: On Fri, May 22, 2009 at 6:24 PM, Chris Jenks ch...@jenks.us wrote: On Fri, 22 May 2009, Alexander Shulgin wrote: Hi, Just flashed the latest images and now I get this on boot: In: /var/cache: No space left on device (+ a few more, /var/lock among them) The phone boots up to om-gta02 login prompt. X doesn't start and usb networking doesn't work either. Tried to reformat uSD card, but this didn't help (didn't expect this to work, however). What can I do about the problem? Anyone else getting the same? -- Alex I didn't even notice the /var/cache problem (wasn't paying attention), and I haven't had any problem with the X server, but I can confirm the usb networking problem - I don't get a usb0 interface on my connected desktop as I did with the testing version from the 9th. Also, I tracked the problem down to the root image - the u-boot and kernel images, flashed back to the working images on the 9th, don't fix the problem. ... Oh, silly me. I just realized I didn't reflash the boot loader. Will try a bit later. As to your usb0 problem, you might want to read the release notes. The fact that it doesn't show up means that finally, the usb0 issue is fixed. Hopefully, you'll never see usb0 again. Congratulations! David -- Alex ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Om2009 testing release 4
On Sat, 23 May 2009, David Fokkema wrote: On Fri, 2009-05-22 at 19:07 +0300, Alexander Shulgin wrote: On Fri, May 22, 2009 at 6:24 PM, Chris Jenks ch...@jenks.us wrote: On Fri, 22 May 2009, Alexander Shulgin wrote: Hi, Just flashed the latest images and now I get this on boot: In: /var/cache: No space left on device (+ a few more, /var/lock among them) The phone boots up to om-gta02 login prompt. X doesn't start and usb networking doesn't work either. Tried to reformat uSD card, but this didn't help (didn't expect this to work, however). What can I do about the problem? Anyone else getting the same? -- Alex I didn't even notice the /var/cache problem (wasn't paying attention), and I haven't had any problem with the X server, but I can confirm the usb networking problem - I don't get a usb0 interface on my connected desktop as I did with the testing version from the 9th. Also, I tracked the problem down to the root image - the u-boot and kernel images, flashed back to the working images on the 9th, don't fix the problem. ... Oh, silly me. I just realized I didn't reflash the boot loader. Will try a bit later. As to your usb0 problem, you might want to read the release notes. The fact that it doesn't show up means that finally, the usb0 issue is fixed. Hopefully, you'll never see usb0 again. Congratulations! David -- Alex I'll check into that. As for the problem with illume not starting, I was able to get it started only after letting the freerunner run for a few hours. Maybe it was too busy during the first minutes after booting to get around to launching illume. Chris ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Om2009 testing release 4
On Fri, May 22, 2009 at 11:35 AM, Alexander Shulgin alex.shul...@gmail.com wrote: On Thu, May 21, 2009 at 10:34 PM, Angus Ainslie nyt...@openmoko.org wrote: Hi, Just flashed the latest images and now I get this on boot: In: /var/cache: No space left on device (+ a few more, /var/lock among them) restart, restart, reflash..? (Often after the flashing a restart is required to finish all configuration things...) Other than that, I have no idea.. r -- | risto h. kurppa | risto at kurppa dot fi | http://risto.kurppa.fi ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Om2009 testing release 4
I didn't see the /var/cache issue, but I just installed on the sd card, rather than flashing. I can say that TR4 is definitely improved over TR3 - very impressive for such a short cycle. There's still a long way to go on the usability side. For example I still haven't figured out exactly where to click to get the option to call or sms someone from my address book - I just kinda blindly poke at the screen in the area above the dial-pad, and eventually the list shows up. I'm going to try using it as my phone for a couple of days, just to see how if I can stand using it instead of QtE... :-) Any info on importing contacts? if I'm going to use it as my daily phone, I'd like to be able to get my contacts in there... Warren On Fri, May 22, 2009 at 12:07 PM, Alexander Shulgin alex.shul...@gmail.comwrote: On Fri, May 22, 2009 at 6:24 PM, Chris Jenks ch...@jenks.us wrote: On Fri, 22 May 2009, Alexander Shulgin wrote: Hi, Just flashed the latest images and now I get this on boot: In: /var/cache: No space left on device (+ a few more, /var/lock among them) The phone boots up to om-gta02 login prompt. X doesn't start and usb networking doesn't work either. Tried to reformat uSD card, but this didn't help (didn't expect this to work, however). What can I do about the problem? Anyone else getting the same? -- Alex I didn't even notice the /var/cache problem (wasn't paying attention), and I haven't had any problem with the X server, but I can confirm the usb networking problem - I don't get a usb0 interface on my connected desktop as I did with the testing version from the 9th. Also, I tracked the problem down to the root image - the u-boot and kernel images, flashed back to the working images on the 9th, don't fix the problem. ... Oh, silly me. I just realized I didn't reflash the boot loader. Will try a bit later. -- Alex ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support -- Warren Baird - Photographer and Digital Artist http://www.synergisticimages.ca ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Om2009 testing release 4
Hi All, As I think we've fixed more things than we broke it's time for another testing release. As usual there are additional instructions here. http://wiki.openmoko.org/wiki/Om2009 There is also a new page for community involvement. Many of these wishlist items need someone to implement them. If you are interested in in owning one of the wishlist items come and join #paroli or send me an email http://wiki.openmoko.org/wiki/Om_2009_get_active Don't bother trying to do an opkg update opkg upgrade to do the upgrade. Chances are you won't get the dependencies right ( I know I didn't ). If you want to preserve your settings use the bind-home method and flash the full image. New in feeds callrec claws-mail dictator dillo midori mokomaze omnewrotate pyring sms-sentry webkit-efl New features Improved call handling - should limit races in oeventsd Better list handling More consistent interface New paroli-illume theme - only change so far is to remove desktop switcher - wanted volunteer to change analog clock to digital - wanted different colour scheme ( maybe white on black to match the rest of paroli ? ) Static MAC addresses for usb devices - usb networking will now show up as ethx on the host side please check dmesg on the host side Ability to cut 30 seconds off boot time - DO NOT use this if you use bind-home - install udev-static-devices to get this speed boost - any solutions on using bind-home and static-devices appreciated Keyboard goes away after use Updated /etc/network/interfaces to give USB0 a metric Added readahead to busybox to test speed increase Known issues Some oeventsd rules are ignored ( framework oeventsd problems ) - don't suspend while plugged in http://trac.freesmartphone.org/ticket/381 - suspend fails after a call http://trac.freesmartphone.org/ticket/435 Bugs fixed 1 pixel wide illume exit menu UTF chars in SMS's - you must still install a keyboard to be able to write different character sets. Keyboard collapses after use Angus ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
